Menu

Individual skill

s4h-writing-report

0upvotes

Writes and audits business reports, briefing documents, and information reports for answer-first structure, precision, hierarchy, and navigability. Use when a report buries its findings, is written for the writer rather than the reader, or lacks clear structure. Triggers: 'write a report', 'report writing', 'business report', 'briefing document', 'information report', 'research summary', 'the report isn't clear', 'buries the findings'.

skills/s4h-writing-report/SKILL.md

Read pinned source

Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
240
Repository last updated
Jul 15, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Writing: Report

Reports fail when they are written for the writer rather than the reader. The writer knows the context, did the work, and wants to show the rigour of the process. The reader needs to know the answer, understand its implications, and decide what to do — usually in less time than the writer spent writing. These are incompatible objectives, and when the report serves the writer's needs, it fails the reader.

The most common report failures:

**Context before answer:** The report explains how the analysis was done before stating what it found. The reader who needs to act has to mine through methodology to find the claim.

**Findings without implications:** The report states what happened but not what it means. "Revenue declined 12% in Q3" is a finding. "Revenue declined 12% in Q3, driven primarily by a 31% drop in enterprise segment that is likely to continue unless the pricing model is revised" is an implication. Readers who need to decide need implications, not just findings.

**Vague quantification:** "Significant growth," "substantial decline," "many customers." These phrases communicate nothing. If a number exists, use it. If it doesn't, acknowledge the absence explicitly.

**Non-navigability:** A report that can only be understood by reading it from beginning to end has failed. The reader who needs the answer to one specific question should be able to find it. Section headers, a clear hierarchy, and an executive summary are not optional niceties — they are the delivery mechanism.
Back to top