Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.
“Write an executive summary of this report: [paste]”“Summarise this document for the board: [paste]”“Create a one-pager from this proposal for the CEO”“Turn these findings into an exec summary”
What to give it
▸Source document or topic — paste or describe
▸Audience — CEO / board / investor / minister / client / committee
▸Decision or action needed — what should the reader do after reading?
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Bottom line in first 3 sentences
✓Standalone — no need to read full document
✓Recommendation is specific
✓Fits length limit
✓Written for audience priorities not author priorities
✓Next steps have owners and dates
⚠️ What it refuses to do
Do not summarise the document chronologically — an executive summary that follows the structure of the source document is not an executive summary, it is an abstract
Do not bury the recommendation at the end — executives read the first paragraph and skim the rest; the ask must be in sentence one or two
Do not use the same summary for different audiences — a CEO and a board member have different decision contexts and require different framing
Do not include background that the reader already knows — every sentence of background must earn its place by making the bottom line more actionable
Do not leave the "risks of inaction" section vague — a summary that does not quantify what happens if the reader does nothing removes the urgency needed for a decision
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
Example output
Input: Summarise: our Q2 retention dropped from 82% to 76% driven by a new onboarding flow that confused mobile users; we shipped a fix in week 10 and retention recovered to 80%; we recommend a full mobile onboarding rework next quarter. · generated by claude-sonnet-4-6