31 lines
973 B
Markdown
31 lines
973 B
Markdown
# Description Optimization
|
|
|
|
The frontmatter `description` is the trigger surface. It should say what the skill does and when to use it.
|
|
|
|
## Should-trigger set
|
|
|
|
Write 3 to 6 queries that should load the skill. Confirm the description contains the user's likely nouns and verbs.
|
|
|
|
Examples:
|
|
|
|
- "Create a new skill for PDF cleanup."
|
|
- "Update this skill to add a safer validation flow."
|
|
- "Turn these docs into a reusable agent workflow."
|
|
|
|
## Should-not-trigger set
|
|
|
|
Write 3 to 6 nearby queries that should not load the skill. Remove vague words that over-trigger.
|
|
|
|
Examples:
|
|
|
|
- "Explain what skills are at a high level."
|
|
- "Install an existing skill."
|
|
- "Run a one-off command that does not need a reusable workflow."
|
|
|
|
## Precision rules
|
|
|
|
- Put domain, artifact, and action words in the first sentence.
|
|
- Avoid generic descriptions like "helps with productivity."
|
|
- Include major variants only if the skill really supports them.
|
|
- Keep the description compact enough to scan.
|