agents-repo--agents-repo-package-creation--package-requirements-analyst

Translates user intent into a structured package blueprint with scaffold arguments and metadata.

3|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/agents-repo/registry --skill agents-repo-agents-repo-package-creation-package-requirements-analyst-agents-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agents-repo--agents-repo-package-creation--package-requirements-analyst
Source: https://github.com/agents-repo/registry/tree/main/.cursor/skills/agents-repo/agents-repo-package-creation/agents-repo--agents-repo-package-creation--package-requirements-analyst
Command: npx skills add https://github.com/agents-repo/registry --skill agents-repo-agents-repo-package-creation-package-requirements-analyst-agents-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague package idea into a concrete, script-ready plan is error-prone: naming rules, metadata fields, and scaffold arguments must all align before any files are created. This Skill converts free-form user intent into a validated package blueprint that downstream agents can execute directly. ## Core Features & Use Cases - Blueprint Generation: Produces a structured blueprint with namespace, package-id, qualified ref, descriptions, tags, owner, and license. - Scaffold Argument Preparation: Outputs the exact arguments for npm run package:create, including --namespace, --package, --template, --name, --description, and --owner. - Cost Estimation: Proposes per-agent, per-flow, and package-level estimateCost values using the registry's 1-10 relative-effort scale with band labels. - Use Case: A user describes wanting a package with two code-review agents and one deployment flow; the Skill returns kebab-case IDs, descriptions, cost bands, an authoring order, and open questions for the package-creator agent. ## Quick Start Ask the analyst to turn your package idea into a blueprint, for example: "Plan a package named dev-tools with two agents for linting and testing and one CI flow."

Frequently Asked Questions about agents-repo--agents-repo-package-creation--package-requirements-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a new agents-repo package before creating files?▼

Describe your package goals in free text and the analyst returns a structured blueprint with namespace, package-id, scaffold arguments for npm run package:create, metadata values, and an authoring order. No files are created during this planning step.

What naming rules apply to package and agent IDs?▼

All IDs must be kebab-case matching the regex ^[a-z0-9]+(?:-[a-z0-9]+)*$. Agent and flow IDs must also be unique across both the agents/ and flows/ directories within the planned package.

What arguments does npm run package:create require?▼

The scaffold requires --namespace, --package, --template, --name, --description, and --owner. In phase 1, the --namespace value must match --owner, and descriptions must be between 1 and 300 characters.

How are estimateCost values assigned to agents and flows?▼

Costs use a relative-effort integer scale from 1 to 10 with band labels: minimal (1-2), low (3-4), moderate (5-6), high (7-8), and critical (9-10). Package-level estimateOverallCost uses band mixed when planned assets span multiple bands.

Does the requirements analyst create or modify any files?▼

No. The analyst only outputs a structured package blueprint as a handoff artifact for the package-creator. It explicitly flags ambiguities and open questions instead of silently resolving them or writing files.