report-writing · vstorm-co — Claude Code skill: what it does, how to install
report-writing provides guidelines for structuring analytical reports, drafting stand-alone executive summaries, and citing sources.
MIT ★ 1,125 updated 2026-10-27
npx skills add vstorm-co/pydantic-deepagents --skill report-writing -a claude-codeWhat report-writing does
This skill outlines a standard architecture for research documents. It splits reports into five parts: a scoped title, an executive summary of two to three paragraphs, logically ordered body sections, conclusions noting study limitations, and an ordered reference list.
Citations follow a strict template: [N] Author/Organization, "Title", URL, Accessed: YYYY-MM-DD. Every numeric claim, quote, or factual statement must feature an inline reference tag immediately after the claim. The guide also asks the model to separate facts from interpretations and write in active voice.
Because the frontmatter specifies auto_load: false, Claude Code does not keep these instructions permanently in its context window. You need to invoke the skill directly when working on research drafts.
What it helps with
- structure raw research into a standardized five-part report
- apply inline numerical citations
[1][2]to all factual claims and data - format bibliographic references with author, title, URL, and access date
- draft a stand-alone executive summary summarizing finished sections
Example prompts for the agent
- Use the report-writing guidelines to turn these raw notes into a cited research report
- Format our research summary following the report-writing rules and add the reference list
How to install report-writing
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill report-writing -a claude-code2Manually: put the files in place
~/.claude/skills/report-writing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/report-writing/
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill report-writing -a codex2Manually: put the files in place
.agents/skills/report-writing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill report-writing -a cursor2Manually: put the files in place
.cursor/skills/report-writing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vstorm-co/pydantic-deepagents apps/deepresearch/skills/report-writing2Manually: put the files in place
.github/skills/report-writing/SKILL.md1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill report-writing -a gemini-cli2Platform CLI
gemini skills install https://github.com/vstorm-co/pydantic-deepagents --path apps/deepresearch/skills/report-writingManually: put the files in place
.devin/skills/report-writing/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about report-writing
How to install report-writing in Claude Code?
Run npx skills add vstorm-co/pydantic-deepagents --skill report-writing -a claude-code in your terminal. You can also place the skill file directly at ~/.claude/skills/report-writing/SKILL.md.
What does report-writing do?
It provides writing rules for research reports, setting formatting conventions, citation requirements, and section hierarchies.
Does this skill load automatically?
No. The skill configuration sets auto_load: false, so it activates only when explicitly called in your prompt.
Source text
SKILL.md · MIT
---
name: report-writing
description: Guidelines for writing well-structured, cited research reports
auto_load: false
---
# Report Writing Guide
## Report Structure
### 1. Title
- Descriptive and specific
- Include the scope or time frame if relevant
- Example: "Advances in Protein Folding Since AlphaFold 3 (2024-2025)"
### 2. Executive Summary
- 2-3 paragraphs summarizing key findings
- Written last, after the full report is complete
- Should stand alone — a reader should understand the main conclusions
### 3. Body Sections
- Organize logically (chronological, thematic, or comparative)
- Each section should address one sub-topic
- Use inline citations [1][2] for every factual claim
- Include data, statistics, and direct quotes where appropriate
### 4. Conclusions
- Synthesize findings across all sections
- Highlight key takeaways and implications
- Note limitations of the research
- Suggest areas for further investigation
### 5. References
- Number references in order of first appearance
- Format: `[N] Author/Organization, "Title", URL, Accessed: YYYY-MM-DD`
## Writing Style
### Clarity
- Use clear, direct language
- Define technical terms on first use
- Prefer active voice over passive
- Keep paragraphs focused on one idea
### Objectivity
- Present evidence before conclusions
- Acknowledge counter-arguments
- Use hedging language for uncertain claims ("suggests", "indicates", "appears to")
- Distinguish between facts and interpretation
### Citation Practices
- Cite every factual claim, statistic, and quote
- Use inline citations [N] immediately after the claim
- Multiple citations for well-supported claims: [1][3][7]
- Never present information without attribution
## Formatting Tips
- Use headers (##, ###) to create clear hierarchy
- Use bullet points for lists of findings
- Use tables for comparative data
- Use blockquotes for direct quotes from sources
- Bold key terms and important findings
© vstorm-co · MIT · vstorm-co/pydantic-deepagents
Similar skills
All skills for Writing and docs →report-writing by other authors comes first.