skill-creator

To create a reusable skill, you define concise metadata and imperative guidance in a SKILL.md file, then package it with optional scripts and references for deterministic execution. This produces a self-contained, distributable skill package.

Valid skill packaging requires concise SKILL.md frontmatter metadata, including trigger descriptions and activation criteria, so the skill can be reliably discovered, validated, and distributed across workflows.

You structure operational instructions by writing clear imperative guidance that directs the assistant through the task, supported by optional scripts, references, and assets to maintain a lean, reusable package.

Yes, you can update an existing skill by refining its metadata, adding supporting scripts and references, and enforcing a package-ready structure to ensure deterministic workflows and reusable context.

The best way to package skills for validation is to ensure a self-contained structure with valid SKILL.md frontmatter, clear operational instructions, and organized assets, making the skill ready for reliable discovery and distribution.

Yes, pyyaml is a required dependency for the skill creation process, enabling the validation and parsing of SKILL.md frontmatter metadata during the packaging and build workflow.