skill-authoringlisted

Author and revise Claude Code skills with calibrated trigger descriptions and eval-gated quality — the description is a trigger surface that competes on fit, not an advertisement that competes on volume. Use when creating a new skill, when an existing skill over- or under-triggers and the description needs rework, when adding negative space ("not for X — that is Y") or example trigger phrasings, when deciding whether a skill body is rigid (bright-line constraints) or flexible (judgment-delegating guidance), or when porting a skill from an imperative register to a neutral one. Covers the calibration doctrine — dense concrete triggers, explicit non-triggers naming the owning sibling, plain-declarative bright lines, descriptive failure-mode catalogs without identity pressure, and the shipping requirement of a trigger dataset with sealed holdout plus a correct-usage rubric for rigid skills. The register linter mechanically enforces the detectable subset of the register rules (banners, caps runs, a fixed phrase li
grimaldost/craft-collection · ★ 2 · AI & Automation · score 68

Install: claude install-skill grimaldost/craft-collection

# Skill Authoring A skill competes for selection in a context window shared with every other installed tool. There are two ways to win: describe your territory precisely, or shout. Shouting works once — then every neighbor escalates, emphasis stops carrying information, and selection quality degrades for the whole toolkit. This doctrine is the first way, made enforceable. This is a **rigid** skill: the description contract, register rules, and shipping requirement are bright lines, each with a mechanical check. ## The description contract The frontmatter `description` is a trigger surface. It has one job: let a model holding only descriptions rank this skill correctly against its neighbors — high when the task is the skill's, low when it is not. 1. **Open with a verb-led capability sentence.** What the skill does and produces, before any trigger list. 2. **Quote the triggers users actually type.** Concrete phrasings ("wrap up", "which tool should handle this"), task shapes, and situations — not abstract categories. Paraphrase variety beats repetition. 3. **Draw the boundary, then name the owner.** Every description ends with negative space: "Not for X — that is Y." Naming the sibling does two jobs: it stops the skill from poaching, and it routes the reader to the right place. 4. **No obedience language.** Descriptions never instruct the model to use them, never inflate stakes, never claim priority over neighbors. A description that needs to demand