skill-manager

To create Agent Skills that follow the SKILL.md specification, draft a markdown file with validated lowercase name and description frontmatter, structure body sections for when to use, steps, examples, and edge cases, and move heavy content into references or assets folders with proper links.

The best way to structure agent skill documentation is to use progressive disclosure by keeping the main SKILL.md concise with clear sections, while moving heavy content, templates, and scripts into dedicated references and assets directories.

To validate frontmatter in a markdown skill file, ensure the metadata includes a lowercase name and a description, along with any optional fields, matching the required specification before the main body content begins.

Yes, you can edit existing agent skills to align with VS Code usage guidelines by updating the SKILL.md structure, validating the frontmatter, and reorganizing heavy content into the references or assets directories.

You need to move content into references or assets folders when the main SKILL.md body becomes too heavy, ensuring that large templates, scripts, or detailed documentation remain linked but do not clutter the primary skill file.

No, setting up a new agent skill does not require external dependencies, as the process relies on creating a skill folder under the designated project directory and authoring a markdown file with the correct frontmatter and structured sections.