skill-creationlisted
Install: claude install-skill AN0099/toothpaste-kit
# When to Use
Any time a new skill is being added to this system, an existing skill is being split into more than one file, or a skill is being renamed. Assumes the worthiness question, is this actually recurring, reusable, complex, and stable enough to earn a skill, is already resolved. That test lives in `skill-discovery`, not here.
# Naming Convention
- Lowercase, hyphen-separated, noun phrase naming the skill's domain, not a verb phrase describing an action: `document-standards`, `working-preferences`, `skill-discovery`. Not `write-documents` or `discover-skills`.
- Two words, occasionally three, matching the existing family (`working-preferences`, `document-standards`, `technical-documents`, `surface-regimes`, `skill-creation`, `skill-discovery`). A name needing more than three words signals the skill's scope is too wide. Narrow it or split it before naming it.
- No version number, date, or status word in the name itself. No `document-standards-v2`, no `skill-creation-draft`. Versioning lives in the skill's own `CHANGELOG.md`. The name describes the domain, which shouldn't change with revisions.
- Check for collision and near-collision before finalizing, not only exact duplicates. `skill-creation` and `skill-create` triggering on similar phrasing is as much a problem as an exact match.
# Required Sections
Every `SKILL.md` in this system follows the same three-position skeleton. Only the middle position varies by skill.
1. **Frontmatter.** `name` and `description` o