Use when authoring a brand-new skill from scratch - turning a capability idea or a "make me a skill that…" request into a complete SKILL.md with a trigger-precise description and the full paid-quality anatomy: procedure, elicitation, thresholds, worked artifact, deliverable, Do NOT, quality bar. Triggers on "write a new SKILL.md from scratch", "turn this capability idea into a complete skill". Do NOT use to review or grade an existing skill (use skill-auditor), to convert an existing prompt (use prompt-to-skill), or for writing unrelated to skills.
Click to play with sound.
---
name: Skill Creator
description: Use when authoring a brand-new skill from scratch - turning a capability idea or a "make me a skill that…" request into a complete SKILL.md with a trigger-precise description and the full paid-quality anatomy: procedure, elicitation, thresholds, worked artifact, deliverable, Do NOT, quality bar. Triggers on "write a new SKILL.md from scratch", "turn this capability idea into a complete skill". Do NOT use to review or grade an existing skill (use skill-auditor), to convert an existing prompt (use prompt-to-skill), or for writing unrelated to skills.
---
# Skill Creator
Turn a capability idea into a committable SKILL.md that meets the paid-quality bar. The costly mistake this prevents: writing a competent essay about the topic instead of an operating procedure - a skill that reads well and changes nothing about the model's output.
## The bar
The skill you write ships only if all of these hold:
- It **fires on exactly the right requests and never on the wrong ones.** The description front-loads concrete triggers a router can act on with no ambiguity.
- It **does not collide** with any existing skill. Before writing, check the catalog for trigger overlap and carve clean boundaries into both descriptions.
- Its body carries the **full anatomy** (skill-author is the canonical standard): framing, ordered procedure, input elicitation, concrete thresholds, at least one worked artifact, an explicit deliverable, a Do NOT section, and a quality bar.
- It is **token-disciplined.** The description loads every session; the body loads on trigger. Every line is paid for by every installer, every session.
- It is **correct and self-contained** - real tools, real paths, real practitioner numbers; no hallucinated capabilities; no context it hasn't established.
## Operating procedure
1. **Find the trigger first.** Before any body text, answer: what exact request should make this fire? Name concrete signals - task verbs, named artifacts, file types, the phrases a user would actually type. If you cannot name them precisely, the skill is not ready to write; press for the real use case.
2. **Check for collisions.** Search the catalog (browse_skills) for skills whose triggers could fire on the same request. Carve the boundary and write it into both descriptions as negative scope. A new skill that steals a neighbor's territory is a defect.