Skip to content
Back to skills

Report Writing

ASecurity

Guidelines for writing well-structured, cited research reports

  • 1,076 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
ai-agents

Security analysis

A100/100

Scanned September 5, 2026

npx -y skills add vstorm-co/pydantic-deepagents --skill report-writing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Report Writing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Report Writing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vstorm-co-report-writing/badge)](https://www.skillsdirectory.com/skills/vstorm-co-report-writing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…