Individual skill
s4h-writing-executive-summary
Produces executive summaries, 1-page briefs, and board-level documents by extracting the situation, key findings, implications, and recommendation — answer-first, one page maximum. Use when a lengthy document needs a senior-audience brief that enables a decision. Triggers: 'executive summary', 'summarise this for a senior audience', '1-page brief', 'TL;DR for leadership', 'distil this', 'board summary', 'write a brief'.
skills/s4h-writing-executive-summary/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- 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)
- 239
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Writing: Executive Summary
Executive summaries fail when they summarise the document rather than answering the reader's question. A summary of a 40-page analysis is not what an executive needs. They need: what is the situation, what are the three things most important to know, what does it mean for their decision, and what should happen next. In that order. In one page.
The fundamental principle: the executive is not the end reader of your analysis — they are a decision-maker who needs the *output* of your analysis in a form that enables action. The detail, the methodology, the full data — that stays in the main document. The executive summary gives them what they need to act without reading the full document.
Four common failures:
- **Summarising the process, not the answer:** "We conducted a comprehensive analysis of three market segments, reviewing 47 data sources over 8 weeks." The executive doesn't need to know how long it took — they need to know what it found.
- **Findings without implications:** Stating what happened without stating what it means for the decision at hand.
- **False balance:** Including minor findings to be thorough, diluting the signal with noise. Three things that matter are better than twelve things that range from critical to marginal.
- **Passive language on the recommendation:** "It may be worth considering..." — the executive summary is where the recommendation is made, not hedged.
---
