u

skill-creator/SKILL.md

@@ -49,7 +49,7 @@ It's OK to briefly explain terms if you're in doubt, and feel free to clarify te
 Start by understanding the user's intent. The current conversation might already contain a workflow the user wants to capture (e.g., they say "turn this into a skill"). If so, extract answers from the conversation history first — the tools used, the sequence of steps, corrections the user made, input/output formats observed. The user may need to fill the gaps, and should confirm before proceeding to the next step.
 
 1. What should this skill enable Claude to do?
-2. When should this skill trigger? (what user phrases/contexts)
+2. When should this skill trigger? Suggest 3–4 natural language phrases the user would actually say — concrete things they'd type, not abstract descriptions. These become the trigger phrases in the skill index.
 3. What's the expected output format?
 4. Should we set up test cases to verify the skill works? Skills with objectively verifiable outputs (file transforms, data extraction, code generation, fixed workflow steps) benefit from test cases. Skills with subjective outputs (writing style, art) often don't need them. Suggest the appropriate default based on the skill type, but let the user decide.
 
@@ -66,7 +66,12 @@ Based on the user interview, fill in these components:
 - **name**: Skill identifier
 - **description**: When to trigger, what it does. This is the primary triggering mechanism - include both what the skill does AND specific contexts for when to use it. All "when to use" info goes here, not in the body. Note: currently Claude has a tendency to "undertrigger" skills -- to not use them when they'd be useful. To combat this, please make the skill descriptions a little bit "pushy". So for instance, instead of "How to build a simple fast dashboard to display internal Anthropic data.", you might write "How to build a simple fast dashboard to display internal Anthropic data. Make sure to use this skill whenever the user mentions dashboards, data visualization, internal metrics, or wants to display any kind of company data, even if they don't explicitly ask for a 'dashboard.'"
 - **compatibility**: Required tools, dependencies (optional, rarely needed)
-- **the rest of the skill :)**
+- **the rest of the skill :)** — at minimum, include:
+  - **Trigger phrases**: 3–4 natural language phrases the user would actually say
+  - **Step-by-step instructions**: Clear steps based on the user's description of ideal output
+  - **Format specifications**: Output format drawn from the interview answers
+  - **Constraints**: Rules or limits from the user's preferences or AGENTS.md
+  - **Example**: Include one if the user provided it. If not, add a note: "Add an example after testing."
 
 ### Skill Writing Guide