skill-creator

To create a self-contained AI workflow Skill, define a SKILL.md file with frontmatter specifying the name and description, then write executable instructions in the Markdown body. You can include optional bundles like scripts, references, and assets that load on demand.

Packaging reusable AI guidelines requires a SKILL.md file where the frontmatter defines accurate metadata and dependencies, and the body contains the core instructions. Optional resource folders for scripts and documentation can be bundled alongside it.

Yes, you can include optional bundles such as scripts, references, and assets when building a custom workflow Skill. These resources are loaded on demand as directed by the instructions within your SKILL.md file.

Yes, a Skill must accurately declare its dependencies and components in the SKILL.md frontmatter before sharing. Quality gates verify this metadata and check for detected risks to ensure safe reuse across other instances.

When updating existing Skill documentation, limitations include ensuring the SKILL.md remains self-contained and that any detected risks in the modified executable instructions are reported to maintain safe reuse across instances.

Skill creation workflows fail quality validation when the SKILL.md frontmatter is missing a defined name or description, or when the Markdown body lacks executable instructions. Inaccurate dependency declarations also trigger validation failures.