/report-writing
Guidelines for writing well-structured, cited research reports
$ npx -y skills add vstorm-co/pydantic-deepagents --skill report-writing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/report-writing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Guidelines for writing well-structured, cited research reports
SKILL.md
report-writing.SKILL.mdname: 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
Read more
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
Open-source, self-hosted Claude Code - a terminal AI assistant and the Python framework behind it. Tool-calling, sandboxed execution, multi-agent teams, skills, checkpoints, unlimited context - on Pydantic AI, any model.
Repo: vstorm-co/pydantic-deepagents
Other skills on pydantic-deepagents.
- /build-and-compile
Building, compiling, and resolving dependency issues across languages
Open skill - /code-review
Systematic code review for bugs, security, style, and performance
Open skill - /data-formats
Working with diverse data formats: binary, text, structured, and custom
Open skill - /environment-discovery
Systematic exploration of unknown environments before starting work
Open skill - /git-workflow
Git operations: commits, branches, PRs, and conflict resolution
Open skill - /performant-code
Writing efficient code that handles large data and tight constraints
Open skill

