agents-repo--agents-repo-package-creation--package-creator

Authors registry package source files with metadata sidecars from an approved blueprint.

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-creator-agents-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agents-repo--agents-repo-package-creation--package-creator
Source: https://github.com/agents-repo/registry/tree/main/.cursor/skills/agents-repo/agents-repo-package-creation/agents-repo--agents-repo-package-creation--package-creator
Command: npx skills add https://github.com/agents-repo/registry --skill agents-repo-agents-repo-package-creation-package-creator-agents-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually authoring registry package source trees is error-prone: frontmatter fields must match metadata sidecars byte-for-byte, cost bands must align with numeric estimates, and IDs must follow strict naming rules. This Skill automates the authoring and revision of every required definition file after scaffolding. ## Core Features & Use Cases - Package Source Authoring: Generates metadata.json, package-root README.md, and paired .agent.md/.metadata.json files for every agent and flow in the blueprint. - Metadata Parity Enforcement: Mirrors duplicated fields between frontmatter and sidecars exactly, enforces MIT licensing, kebab-case IDs, and estimateCost band ranges. - Correction Handling: Applies reviewer and validation feedback from package-submission-reviewer, package-script-runner, and package-release-gate stages. - Use Case: After scaffolding a new registry package, feed the approved blueprint to this Skill to produce the complete, validation-ready source tree without hand-editing dozens of files. ## Quick Start Use the package creator skill to author all agent and flow definition files from this approved package blueprint.

Frequently Asked Questions about agents-repo--agents-repo-package-creation--package-creator

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

FAQPage Schema
How do I create agent and flow definition files for a registry package?▼

Provide an approved package blueprint after scaffolding. The Skill generates one .agent.md and one .metadata.json pair per agent and flow, plus package-level metadata.json and README.md, with all required frontmatter fields and ordered body sections populated.

How do I keep frontmatter and metadata.json sidecars in sync?▼

The Skill mirrors every duplicated field between each .agent.md frontmatter and its .metadata.json sidecar byte-for-byte. This includes name, license, version, and estimateCost values, eliminating manual drift between the two files.

What naming rules apply to agent and flow IDs?▼

IDs must match the kebab-case pattern ^[a-z0-9]+(?:-[a-z0-9]+)*$ and be unique across both agents/ and flows/ directories. The frontmatter name must exactly equal the .agent.md file stem, and namespaced or qualified IDs are not allowed.

How are estimateCost bands validated in package metadata?▼

Each sidecar's estimateCost.band must match its estimatedCost integer per registry ranges: minimal 1-2, low 3-4, moderate 5-6, high 7-8, critical 9-10. Package-level estimateOverallCost uses band mixed when child assets span multiple bands.

What files are outside the package authoring scope?▼

The Skill does not generate versions/ snapshots, ZIP archives, checksums, or detail.json. Those artifacts are produced later by the package:build step, which also copies the root README.md into the snapshot.