executive-summary
Skill1 starsChanged 38 days agoMITView on GitHub
Compresses long reports, memos, and analyses into a decision-ready one-page summary (250-350 words) - bottom line up front, 3-5 evidence-backed key findings, a specific owned-and-dated recommendation, risks with mitigations, and the exact decision or resource being requested - plus a separate list of unverifiable claims to probe. Use when someone says "summarize this report for the exec team", "give me a one-pager on this analysis", "write the BLUF for this memo", or a leader needs to act on a document in 90 seconds. Do NOT use for narrating data and charts into an insight story - use data-story instead - or for recurring project status - use stakeholder-update instead.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- jonmagic/skillstheir own version, first seen Nov 8, 2026
- Nomanriaz786/claude-consulting-teamtheir own version, first seen Nov 1, 2026
- microsoft/aibast-agents-librarytheir own version, first seen Oct 13, 2026
- poorvith-mp/skills-writingtheir own version, first seen Aug 19, 2026
- kayspiegel/survey-insight-skillstheir own version, first seen Aug 16, 2026
- zrosenfield/sharepoint-ai-skillstheir own version, first seen Aug 4, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- zrosenfield/sharepoint-ai-skills★ 96same name
- devstefancho/skills★ 13same name
- microsoft/aibast-agents-library★ 8same name
- jonmagic/skills★ 6same name
- kayspiegel/survey-insight-skills★ 2same name
- Nomanriaz786/claude-consulting-team★ 1same name
- CAPP-Financials/Consulting_Brain★ 0same name
- poorvith-mp/skills-writing★ 0same name
- sted9000/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read the full source. Identify the single decision or question it serves.
- Distinctive: line 33
Every claim carries evidence: a number, a source, or a date.
- Distinctive: line 34
Use the active voice and present tense.
- Distinctive: line 35
No jargon the reader's boss wouldn't use.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Executive Summary
You compress reports, memos, and analyses into a one-page summary an executive can read in 90 seconds and act on.
Core principle
Executives read to decide, not to learn. Lead with the conclusion. Everything else supports it.
Process
- Read the full source. Identify the single decision or question it serves.
- Extract: the bottom line, 3-5 supporting findings, the recommendation, and the cost of inaction.
- Draft top-down. The first sentence is the answer.
Structure (one page, in this order)
- Bottom line up front (BLUF) - 1-2 sentences. The conclusion and what you're asking for.
- Key findings - 3-5 bullets, each a single insight with one number or fact attached.
- Recommendation - what to do, who owns it, by when.
- Risks / trade-offs - 2-3 bullets. What could go wrong and the mitigation.
- What we need from you - the specific decision, approval, or resource.
Rules
- One page. If it spills over, you haven't decided what matters.
- Every claim carries evidence: a number, a source, or a date. No "significant improvements."
- Use the active voice and present tense. "Revenue grew 18%" not "It was found that revenue had grown."
- No jargon the reader's boss wouldn't use.
- Numbers in numerals (18%, $2.4M, 3 weeks). They scan faster.
Insight extraction
A finding is not a fact; it's a fact plus its meaning. "Churn is 7%" is a fact. "Churn is 7%, double the industry benchmark, and concentrated in month-two users" is a finding. Always push to the second form.
Recommendation discipline
- Be specific enough to act on. "Improve onboarding" is not a recommendation; "Add a guided setup to the first session, owned by Product, shipping Q3" is.
- State the expected outcome and how you'll measure it.
Length guidance
- BLUF: 25-40 words.
- Each finding bullet: under 25 words.
- Whole summary: 250-350 words.
Anti-patterns
- Burying the recommendation at the bottom.
- Hedging everything ("it may possibly suggest"). Take a position; note uncertainty once.
- Restating the document's structure instead of its conclusions.
Output
Deliver the one-pager. Then list, separately, any claims from the source you could not verify so the reader knows what to probe.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.