Setting the file. One moment.
Use this path to improve skill triggering quality and reduce false matches.
- Draft a description with realistic user language and concrete trigger phrases.
- Build two query sets:
- should-trigger queries
- should-not-trigger queries
23.10
Example Hook Backed Skill
- Check the current description against both sets.
- Edit description wording to improve precision/recall.
- Repeat until false positives and false negatives are reduced to acceptable levels.
- Keep the description in third person.
- Include what the skill does and when to use it.
- Avoid implementation details that do not help triggering.
- Avoid provider-specific phrasing unless the skill is intentionally provider-specific.
- For provider-agnostic skills, avoid naming Claude, Codex, or any provider in ways that would narrow portability expectations.
- Final description text
- should-trigger query set
- should-not-trigger query set
- Summary of edits made to improve trigger behavior
references/description-optimization.md