write-a-skill

Authoring Wunderkind-native skills requires creating a skills/<skill-name>/SKILL.md file with required frontmatter for name and description, plus defined triggers, anti-triggers, filesystem scope, and ownership metadata.

To add references and scripts to a Skill Unit, place optional resources like REFERENCE.md, EXAMPLES.md, and supporting evidence or durable learnings under the .sisyphus directory within the skills/<skill-name> folder structure.

The mandatory frontmatter fields when creating a new SKILL.md file are name and description, which align the Skill Unit with the central skill standard and ensure correct trigger surfaces and filesystem scope enforcement.

Defining triggers and anti-triggers improves maintainability by setting clear boundaries for when a skill should activate or remain dormant, ensuring the filesystem scope and standard workflow are enforced without overlapping with other Skill Units.

No external dependencies are required to write a Wunderkind-native skill; the process relies on repo-local standards, defining ownership, triggers, and optional references directly within the skills/*/SKILL.md layout.

Use this guide when you need to enforce the central skill standard for frontmatter, filesystem scope, and ownership, ensuring well-scoped and maintainable Skill Units rather than manually guessing the correct directory layout.