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'.

242 stars 25 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add human-avatar/skills-for-humanity --skill s4h-writing-executive-summary
Manual install
git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git /tmp/skills-for-humanity
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-humanity/skills/s4h-writing-executive-summary ~/.claude/skills/s4h-writing-executive-summary

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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.

---

## Your Process
Read the full skill on GitHub

Details

Skill name
s4h-writing-executive-summary
Path
skills/s4h-writing-executive-summary/SKILL.md
License
MIT
Repo updated
15 July 2026

FAQ

What does the S4h Writing Executive Summary skill do?

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'.

How do I install the S4h Writing Executive Summary skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add human-avatar/skills-for-humanity --skill s4h-writing-executive-summary. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is S4h Writing Executive Summary popular?

It lives in human-avatar/skills-for-humanity, which has 242 GitHub stars and 25 forks, and is included in 1 curated skill list.

Related skills

S4h

242

human-avatar/skills-for-humanity

Master orchestration skill. Takes any situation in plain English, identifies the underlying goal, designs a multi-skill reasoning workflow, and executes it sequentially — feeding each skill's output into the next. Use when you say 'help me think through this', 'I need to figure out what to do', 'where do I start', or any time you want structured thinking applied end-to-end rather than routed to a single tool.

Testing & QAIn 1 list25

S4h Aesthetic

242

human-avatar/skills-for-humanity

Entry point for the aesthetic toolkit. Routes to the right aesthetic skill based on your situation. Use when you say 'aesthetic', 'check the design', 'does this feel right', 'is this elegant', 'is this too complex', 'what pattern is this', 'find the simpler version', or want an aesthetic lens applied without knowing which specific tool fits.

OtherIn 1 list25

S4h Aesthetic Coherence Check

242

human-avatar/skills-for-humanity

Tests whether the parts of something form a unified whole — finding the jarring inconsistencies that accumulate when different contributors work without a shared vision. TRIGGERS: 'coherence check', 'does this feel unified', 'something feels off', 'inconsistent', 'check the whole', 'does this hang together'.

Testing & QAIn 1 list25

S4h Writing Inconsistency Audit

242

human-avatar/skills-for-humanity

Runs four systematic passes to identify timeline errors, character logic violations, world-rule breaks, and physical continuity errors. Use when a manuscript has contradictions, continuity problems, or logic violations. Triggers: 'there are contradictions', 'continuity errors', 'inconsistency check', 'the character shouldn't know that', 'timeline doesn't add up', 'continuity audit', 'inconsistencies in the manuscript'.

Writing & ContentIn 1 list25

S4h Writing Dialogue

242

human-avatar/skills-for-humanity

Diagnoses and repairs dialogue for subtext, voice differentiation, exposition, and forward momentum. Use when dialogue sounds wrong, on-the-nose, or when characters all sound the same. Triggers: 'the dialogue sounds wrong', 'dialogue feels on the nose', 'dialogue review', 'characters sound the same', 'dialogue fix', 'dialogue is too direct', 'the dialogue explains too much'.

Writing & ContentIn 1 list25

S4h Writing Line Editing

242

human-avatar/skills-for-humanity

Applies five-category line-editing passes to identify and repair redundancy, nominalisations, passive voice, rhythmic monotony, and throat-clearing. Use when prose is clunky, wordy, or mechanically flawed. Triggers: 'the sentences are clunky', 'line editing', 'the prose is wordy', 'tighten this up', 'sentence-level editing', 'too many passive constructions', 'the writing is verbose'.

Writing & ContentIn 1 list25

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.