Step 5 of 5
Tune It So It Fires When You Expect
Adjust the description so the skill triggers on the right requests, and not the wrong ones.
Triggering is entirely driven by the description. If a skill fires too rarely, the description is too narrow or too abstract. If it fires when it should not, the description is too broad.
A description that triggers well
- Starts with "Use when…" and names the concrete situation.
- Uses the words a user would actually say ("release note", "changelog", "user-facing").
- States the boundary (when NOT to use it) if there is a nearby look-alike task.
# too narrow: only fires on the exact phrase
description: Use for release-line formatting.
# well-scoped: fires on the real situations, names the words users use
description: Use when turning a rough internal changelog note or commit
message into a polished, user-facing release-notes line.