Triggers on "executive summary", "resumen ejecutivo", "write executive brief", "summarize for C-level". Distills complex information into 1-page executive summaries with key metrics, decision points, and recommended actions. Output: formatted executive summary in markdown or HTML. [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
TL;DR — Transforms complex, multi-page content into crisp one-page executive summaries that surface decisions, metrics, and actions for time-constrained senior leaders.
Invoke this skill when any of these conditions are met:
| Signal | Examples |
|---|---|
| Summarization request | "Write an executive summary of this report", "Resumen ejecutivo" |
| C-level preparation | "Summarize this for the board", "Brief the CEO on project status" |
| Decision framing | "Distill the options into a one-pager for the leadership team" |
| Document condensation | "Turn this 40-page analysis into something a VP will read" |
Do not activate for meeting minutes (use meeting-notes), sprint reports (use sprint-report), or detailed technical documentation where brevity would compromise safety-critical information.
Before writing, analyze the input material:
If the source material is ambiguous or incomplete, state assumptions with [INFERRED] tags and flag gaps with [OPEN].
The skill uses the BLUF (Bottom Line Up Front) structure optimized for executive attention patterns:
The single most important takeaway. Answers the question: "If the reader stops here, what must they know?" This is the BLUF — state the conclusion, recommendation, or status first.
Minimal background needed to understand the opening statement. Assume the reader has strategic context but not operational detail. Reference time period, scope, and triggering event.
Maximum 5-7 metrics in a compact table. Each metric includes: Metric Name, Current Value, Target/Benchmark, Status (on-track, at-risk, off-track). Only include metrics that directly support the narrative.
If decisional: frame each option with pros, cons, and recommendation. Bold the recommended option. If informational: list the top findings in order of strategic importance. If action-oriented: list the requested approvals or actions.
Only the risks that would change the executive's decision or escalate their attention. Each risk includes probability indicator and mitigation status.
Concrete, time-bound next steps with assigned owners. Framed as requests: "Approve X by date Y" or "Direct team Z to begin phase 2."
Single line referencing the full source document for readers who want depth. Format: "Full analysis: [document name], [page count] pages, [date]."
These principles govern the output quality:
[EXPLICIT], [INFERRED], or [OPEN] tags.@media print rules.Executive Summary | {source document} | {date} | Generated by executive-summary skill.| Dimension | Priority | Rationale |
|---|---|---|
| Clarity | HIGHEST | Ambiguity is the enemy of executive communication |
| Brevity | HIGH | One page is a hard constraint, not a suggestion |
| Accuracy | HIGH | Misrepresented data destroys trust instantly |
| Completeness | MEDIUM | Deliberately sacrificed for brevity; point to the full document |
| Visual polish | MEDIUM | Clean formatting aids scanning but substance wins |
[OPEN] item. [EXPLICIT][OPEN].Good output (excerpt):
## Executive Summary: Project Atlas Q1 Status
Project Atlas is on track to deliver Phase 1 by June 2026, with 73%
of milestone deliverables completed. Budget utilization is at 68%
against a 75% plan, indicating a favorable variance. One critical
risk requires board attention: the vendor contract for the data
platform expires April 30 with no renewal signed. [EXPLICIT]
| Metric | Current | Target | Status |
|--------|---------|--------|--------|
| Milestone completion | 73% | 75% | On track |
| Budget utilization | 68% | 75% | Favorable |
| Team attrition | 2 of 14 | 0 | At risk |
| Customer pilot signups | 12 | 10 | Ahead |
**Recommended Actions:**
1. **Approve vendor contract renewal** by April 15 to avoid
platform access disruption. Owner: VP Engineering. [EXPLICIT]
2. Backfill two departed engineers by Sprint 8. Owner: HR. [EXPLICIT]
Bad output (excerpt):
## Summary
The project is going well overall. We have done a lot of work and
things are mostly on schedule. There are some risks but the team is
handling them. We recommend continuing as planned.
The good example leads with the bottom line, provides a scannable metrics table with status indicators, and closes with specific, time-bound actions and owners. The bad example is vague, unquantified, and gives no actionable information.
Before delivering the executive summary, confirm every item:
| File | Purpose |
|---|---|
references/bluf-template.md | BLUF framework template with section prompts |
references/body-of-knowledge.md | Executive communication best practices and BLUF methodology |
references/html-template.html | Print-optimized HTML template for executive summaries |
evals/evals.json | Evaluation scenarios for summary quality, compression ratio, and accuracy |
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.