write-a-skill

Name: write-a-skill
Availability: InStock
Author: grant-vine

Author Wunderkind-native skills with required frontmatter and triggers under skills/*/SKILL.md.

1|Updated Mar 6, 2026

Search Tags:#triggers #filesystem #authoring #scripts #skill #references #wunderkind

Ready to run

npx skills add https://github.com/grant-vine/wunderkind --skill write-a-skill-grant-vine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/grant-vine/wunderkind/tree/main/skills/write-a-skill
Command: npx skills add https://github.com/grant-vine/wunderkind --skill write-a-skill-grant-vine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoring Wunderkind-native skills requires a clear, repo-local standard that defines owner, trigger surfaces, filesystem scope, and optional references or scripts; this guide helps teams produce well-scoped, maintainable Skill Units.

Core Features & Use Cases

Defines the required frontmatter (name and description) and the expected layout for skills under skills/*/SKILL.md.
Documents how to add optional resources like REFERENCE.md, EXAMPLES.md, and supporting evidence or durable learnings under .sisyphus.
Sets expectations for ownership, scope, triggers, anti-triggers, and how to align with the central skill standard.

Quick Start

Create a new skills/<skill-name>/SKILL.md following the standard, including name, description, triggers, and optional references, scripts, and assets as needed.

Frequently Asked Questions about write-a-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the required structure for authoring Wunderkind-native skills?▼

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.

How do I add optional references and supporting scripts to a Skill Unit?▼

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.

What frontmatter fields are mandatory when creating a new SKILL.md file?▼

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.

How does defining triggers and anti-triggers improve skill maintainability?▼

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.

Do I need external dependencies to write a Wunderkind-native skill?▼

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.

When should I use write-a-skill versus manually structuring a skill directory?▼

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.