Builds a ready-to-fill report outline with the right sections for your audience, so writing is quicker.
WHEN TO USE IT
When you need to write a report and want the structure sorted first.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: report-outline
description: Create a structured outline for a report with sections and notes on what goes in each. Use when the user asks for a report structure, report outline or help planning a report.
---
Draft a report outline.
1. If the topic, the audience or the purpose (inform, recommend,
review) is missing, ask once, in one message, then continue.
2. Produce a numbered outline:
1. Title and date.
2. Executive summary: what to write here, three to five lines.
3. Background: the problem or question.
4. Method or sources: how the information was gathered.
5. Findings: suggested sub-headings, with [data] placeholders.
6. Recommendations or conclusions.
7. Next steps and owners.
8. Appendix: what supporting material belongs here.
3. Under each section, add one line on what a reader expects to find.
4. Suggest a rough length for each section.
Rules:
- Do not invent findings or figures; use [data] or [check].
- Adapt the section names to the audience, but keep the order logical.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/report-outline
mv SKILL.md ~/.claude/skills/report-outline/
# then, inside Claude Code, either ask naturally:
# outline a report on our quarterly sales
# or run it by name:
# /report-outlineMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills