Write a Trigger-Worthy Description
The description is the trigger. Use the user's words, and say when to skip.
A skill's description IS its trigger. The agent reads it on every turn and decides whether the current task matches. Vague descriptions fire on the wrong tasks; absent descriptions never fire at all. Lead with the concrete verbs and nouns the user would type — 'review a pull request', 'set up a new GitHub issue tracker', 'draft a PRD from this conversation'. Then add a line about what the skill explicitly should NOT do, so it skips weak matches instead of grabbing them.
Where you'll practice this
One Promptles scenario teaches this principle directly.
The Trigger Description
Your team uses Claude Code and wants to standardize how engineers convert a Slack/PR discussion into a product-requirements doc. You're authoring a `to-prd` skill — a markdown file with frontmatter (`name`, `description`) and a body that walks the agent through drafting a PRD…