Skill Build Kit — Terminology
Locked Terms
| Term | Means | NOT |
|---|---|---|
| Skill | A Claude .md file the user uploads and runs | App, tool, bot, GPT, template, prompt |
| Brief / Scorecard / Tracker | The output the skill produces (varies per skill) | Report, analysis, assessment, audit |
| Run | What the user does with the skill | Use, try, test, execute |
| Paste | How the user provides input | Upload, import, enter, input |
| Install | Adding the skill to Claude (one-time) | Set up, configure, onboard |
| Trigger phrase | The natural language command that activates the skill | Prompt, command, instruction |
| Output format | The template section of the skill that defines exact structure | Schema, spec, layout |
| Core principle | The one operating rule that drives output quality | Philosophy, approach, methodology |
| Practice | The user's business | Company, firm (OK occasionally), business (too generic) |
| Practice owner | The person we're talking to | Founder, entrepreneur, solopreneur, business owner |
Skill File Voice
The skill file is an instruction document, not marketing copy. It tells Claude how to think and what to produce. Voice should be:
- Direct and specific — every section describes exactly what to do
- Rules-oriented — constraints are stated as rules, not suggestions
- Format-explicit — output structure is shown, not described
- No hedging — "Do this" not "You might want to consider"
The "What Makes This Different" section is the exception. This is the one section that speaks to the user (not to Claude). It should use the same voice as delivery page copy — pattern-revealing, specific, grounded.
Quick-Start Guide Voice
The quick-start is a setup document for someone who just received a free skill. Voice should be:
- Casual and brief — "Here's how to use it" not "Welcome to your new skill"
- Step-numbered — every action is a numbered step
- Assumption-free — don't assume they know what Skills are or where Settings lives
- Tips from experience — "More emails = better brief" not "For optimal results, include additional correspondence"
Forbidden Constructions (Skill File)
| Don't Write | Write Instead |
|---|---|
| "This skill will help you..." | [State what it does: "Produces a structured brief from client emails"] |
| "Consider including..." | "Include both sides of the conversation." |
| "For best results..." | [State the rule: "One client per run."] |
| "The skill leverages..." | [State the mechanism: "The skill reads all emails before producing output."] |
Forbidden Constructions (Quick-Start)
| Don't Write | Write Instead |
|---|---|
| "Welcome to your new skill!" | "You just got a free Claude skill. Here's how to use it." |
| "For optimal performance..." | "More emails = better brief." |
| "Please ensure you have..." | "What You Need: A Claude Pro account..." |
| "You're all set to go!" | "That's it. The skill is installed." |