agentsclimarketplace

Executive summary

Skill SkillMedev/skills/skills/executive-summary

The open Skill Me catalog — every hosted skill as a portable, MIT-licensed SKILL.md

Install
npx -y skills add SkillMedev/skills --skill executive-summary

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.9 KB, as published. Nobody here has run it

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

  1. Read the full source. Identify the single decision or question it serves.
  2. Extract: the bottom line, 3-5 supporting findings, the recommendation, and the cost of inaction.
  3. Draft top-down. The first sentence is the answer.

Structure (one page, in this order)

  1. Bottom line up front (BLUF) - 1-2 sentences. The conclusion and what you're asking for.
  2. Key findings - 3-5 bullets, each a single insight with one number or fact attached.
  3. Recommendation - what to do, who owns it, by when.
  4. Risks / trade-offs - 2-3 bullets. What could go wrong and the mitigation.
  5. 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.

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06

  • announce the skill at startin 54 of 1637, across 21 files
  • convert legacy doc files before editingin 45 of 1637, across 7 files
  • predict questions readers might askin 42 of 1637, across 3 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test document with fresh context-less instancein 42 of 1637, across 3 files
  • ask interview questions one at a timein 42 of 1637, across 26 files
  • include exact file paths in every taskin 42 of 1637, across 15 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 1 file

Said here and by no other author read

  • Identify the single decision the source serves
  • Extract three to five evidence-backed key findings
  • Specify who owns the recommendation and by when
  • State expected outcomes and how to measure them
  • Attach a number, source, or date to every claim
  • Keep the whole summary between 250 and 350 words

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.