← Browse

@vstorm-co/report-writing

A

Guidelines for writing well-structured, cited research reports

skillclaude

Install

agr install @vstorm-co/report-writing --target claude

Writes 1 file into .claude/skills/, pinned to git-e520b928.

  • .claude/skills/report-writing/SKILL.md

Document


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

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-e520b92847072026-07-31