| name | skill-name-in-kebab-case |
| description | One sentence describing WHAT this skill does and WHEN Claude should use it. This is the single most important field — Claude only loads a skill when the description matches the user's request, so lead with concrete trigger phrases and task types. Aim for 1–3 sentences. Bad example: "Helps with QBRs." Good example: "Drafts a quarterly business review deck from a completed quarter's sales data. Use when the user says 'draft a QBR,' 'build a QBR deck,' or pastes a CSV of quarterly numbers and asks for slides." |
{{Human-readable skill name}}
When to use this skill
List the concrete user requests that should trigger this skill. Three to five
examples, phrased the way a user would actually phrase them:
- "Draft a QBR deck for Q3 using this data"
- "Build me slides for the quarterly review"
- "Turn these numbers into a QBR"
When NOT to use this skill
Just as important. If there's an adjacent skill that handles a related-but-
different job, say so here so Claude doesn't grab the wrong one.
- Not for monthly business reviews — those use the
draft-mbr-deck skill.
- Not for sales forecasts — those use the
build-forecast skill.
Procedure
Step-by-step instructions Claude should follow when this skill is active.
Keep each step concrete and checkable.
- Ask the user for the quarter, the data source, and the audience if they
weren't provided.
- Validate the data: required columns are [...]. If any are missing, stop and
tell the user what's missing before proceeding.
- Compute [...] and flag any quarter-over-quarter change greater than X%.
- Draft the deck with the following slide structure: [...]
- Output as
.pptx using the pptx skill. Do not fabricate numbers — if a
value is missing from the source data, write "TBD" in the slide.
Output format
Be explicit about what the user should get back. File type, structure, length,
tone.
- Deliverable: a
.pptx file, 8–12 slides.
- Tone: executive-facing, data-forward, no marketing language.
- All figures must cite the source row/range from the input data.
Data handling reminders
The org-wide Organization Preferences already cover credential and PII rules.
Restate anything specific to this workflow:
- Customer logos on slides are fine only if they come from the approved brand
kit at {{BRAND_KIT_URL}}.
- Do not include individual rep names or individual deal sizes on slides that
will be shared outside the sales org.
Examples
Example 1 — happy path
User: "Draft a Q3 QBR deck from this CSV." (attaches q3_sales.csv)
Claude (following this skill): (validates columns, computes deltas,
produces an 8-slide pptx)
Example 2 — missing data
User: "Draft a Q3 QBR." (no data attached)
Claude: "Happy to — which data source should I use, and who's the
audience (exec team, board, all-hands)?"
Supporting files
If the skill needs reference files (templates, schemas, example outputs),
list them here and include them in the skill folder:
templates/qbr-template.pptx — the brand-approved layoutschemas/sales-data-schema.json — required CSV columns
