skill-creator

To structure an AgentSkill for modularity, outline its core logic in SKILL.md while moving supplementary content into dedicated directories like references, scripts, and assets, enforcing progressive disclosure to keep the main file concise and scalable.

Auditing existing AgentSkills involves validating the structure against the spec, checking resource organization, and moving misplaced content into appropriate references, scripts, or assets folders to ensure packaging practices are tidy and reusable.

Packaging an AgentSkill from scratch involves initializing from a template, customizing the SKILL.md frontmatter with the name and description, and organizing required resources before final validation.

No external dependencies are required to create and edit AgentSkills, as the workflow relies on defining SKILL.md frontmatter and organizing internal resources like scripts and assets natively.

You should move content to references or assets when the main SKILL.md becomes overloaded, ensuring progressive disclosure by separating detailed documentation and static files from the primary processing logic.