exec-summary
Skill4 starsChanged 33 days agoMITView on GitHub
Compress a long document (SOW, report, assessment, change request) into a one-page executive summary for a C-suite or board audience. Use when a decision-maker will not read the full document. Usage - /exec-summary path/to/document.md -- audience notes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- itgenius-au/skills-librarytheir own version, first seen Nov 1, 2026
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
- modeled-information-format/mif-docs-plugintheir own version, first seen Oct 8, 2026
- Jiplet/transformation-ostheir own version, first seen Jul 2, 2026
- janellecipriano/pm-skillstheir own version, first seen Jun 23, 2026
- hamzafarooq/claude-code-startertheir own version, first seen May 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- indranilbanerjee/digital-marketing-pro★ 934same name
- hamzafarooq/claude-code-starter★ 145same name
- Jiplet/transformation-os★ 2same name
- itgenius-au/skills-library★ 1same name
- janellecipriano/pm-skills★ 1same name
- modeled-information-format/mif-docs-plugin★ 1same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-requestSkill
- code-review-lightSkill
- deliverable-qaSkill
- meeting-prepSkill
- sow-reviewSkill
- stakeholder-prepSkill
- status-commsSkill
- status-reportSkill
- transcript-actionsSkill
- weekly-briefSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
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 19
Read the whole document before summarizing.
- Distinctive: line 50
Use concise, executive-level prose.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Compress a long document into a tight one-page executive summary. Written for a C-suite or board audience who will not read the full document.
Input
$ARGUMENTS is the path to the document, optionally followed by audience context after --:
/exec-summary sample-projects/globex-erp-migration/sow.md -- audience is the CFO, focus on cost and timelineRead the whole document before summarizing. If no path was given, ask for one.
Output
Executive Summary: [Document Title] Prepared for: [Audience if specified | Senior Leadership] Date: [Today's date]
Situation (2 to 3 sentences): What is this document about? What decision or context does it address?
Key Findings / What's in This Document:
- 3 to 5 bullets covering the most important points
- Lead with the "so what": not just what it says, but why it matters
Risks or Open Issues:
- Top 2 to 3 risks, gaps, or items requiring attention or decision
Recommendations / Proposed Next Steps:
| Recommendation | Owner | Target Date |
Bottom Line: One sentence. If the reader remembers one thing from this document, it should be this.
Drafted with Claude Code on YYYY-MM-DD; reviewed by [NAME]
Use concise, executive-level prose. No jargon without explanation. Bullets 12 words or fewer. The total summary should fit on one printed page (roughly 350 to 450 words). Every figure in the summary must appear in the source document; do not round, extrapolate, or combine numbers.
Example Output
Executive Summary: Acme Corp Data Warehouse SOW Prepared for: CFO and Project Sponsor Date: May 8, 2025
Situation: This Statement of Work defines the scope, timeline, and pricing for a 6-month data warehouse modernization project. It replaces Acme's on-premise SQL Server environment with a cloud-based Snowflake platform to support faster reporting and analytics.
Key Findings:
- Total contract value: $485,000 fixed-price
- Go-live target: December 12, 2025 (assumes client data access by June 1)
- Three workstreams: data migration, reporting layer, and user training
Risks or Open Issues:
- Acceptance criteria are not defined; "fully functional" language creates ambiguity
- Change control process is absent; any scope additions will require a CR process to be established
Bottom Line: The SOW is directionally sound but needs two additions before signing: defined acceptance criteria and a change control clause.
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.