Menu

Individual skill

formatted-report-writer

0upvotes

Produces long-form business and consulting reports with a standalone executive summary, three-level heading hierarchy, and skimmability rules that let a busy reader navigate in under two minutes. Use when someone asks "write up this analysis as a report", "structure my strategy brief", "turn these findings into a client deliverable", or "make this document skimmable for executives". Do NOT use for presenting user-research findings to a product team - use research-readout instead; for a one-paragraph-to-one-page condensation of an existing document, use executive-summary; for slide-based delivery, use slide-deck-builder; for academic papers, use academic-essay.

skills/formatted-report-writer/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

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 6, 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)
24
Repository last updated
Oct 13, 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

# Formatted Report Writer

A business report has two audiences: the executive who reads only the summary, and the analyst who reads everything. The costly failure this skill prevents is the report that serves neither - findings buried in chronology, a summary that teases instead of concludes, and a busy reader who gives up before reaching the recommendation they were supposed to approve.

## Operating procedure

### Step 1: Gather inputs - do not draft until these are settled

Answer in one sentence each; if the requester cannot, propose an answer and label it a guess:

1. What decision or action does this report enable?
2. Who is the primary reader, and what do they already know?
3. What must the reader believe by the end?
4. Register: formal (board, regulatory) or plain (internal ops)? Default: plain.
Back to top