Individual skill
executive-summary-writer
Distills dense technical postmortems, architecture RFCs, and quarterly engineering metrics into crisp C-suite briefs.
skills/documentation/executive-summary-writer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
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 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)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 591 bytesSKILL.mdcore · 1,567 bytesexamples/example.mddoc · 1,476 bytes
Read excerpt
## Purpose
Translate complex, jargon-heavy technical documents (incident postmortems, multi-quarter migration plans, architecture RFCs) into concise, high-impact executive summaries for CTOs, VPs, and non-technical stakeholders.
## When to Use
- Communicating major production outage postmortems to company leadership.
- Pitching large infrastructure investments requiring budget sign-off.
- Preparing quarterly engineering board updates and business impact reviews.
## What to Analyze
1. **Bottom Line Up Front (BLUF)**: What happened, what does it cost, and what is required in 2 sentences.
2. **Business Impact**: Quantify downtime, lost revenue, customer trust impact, and SLA penalty risks.