Every skill must live in its own directory containing a SKILL.md file:
skills/
└── my-new-skill/
└── SKILL.md
Your SKILL.md must include all of the following:
- Title —
# Skill Name — One-Line Description - Role — What the skill does, written as a system prompt
- Trigger Conditions — Keywords and phrases that activate the skill
- Workflow / Pipeline — Step-by-step instructions with YAML configs where applicable
- Example — A concrete input → output walkthrough
- Metadata — Skill ID, version, author, license, last updated, compatibility
- Error Handling — 5-step standard: retry → degrade → log → escalate → never silent
- Changelog — Versioned history of changes
- No broken dependencies — skills must be self-contained
- Concrete examples with realistic data flows
- YAML configs for any parameterized behavior
- Integration points listed (MCPs, APIs, tools)
- Guardrails and safety limits defined
- Directory names:
kebab-case - Skill IDs:
tkm-{skill-name} - Categories:
custom-skills/orcombination-skills/
- Fork this repo
- Create a branch:
git checkout -b skill/my-new-skill - Add your skill directory and
SKILL.md - Run the installer locally to verify symlinks work
- Open a PR with a description of the skill's purpose and trigger conditions
Follow semver: MAJOR.MINOR.PATCH
- MAJOR: Breaking changes to trigger conditions or output format
- MINOR: New capabilities, new integration points
- PATCH: Bug fixes, documentation improvements