Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/executive-summary-generator

@9449d36
Run it yourself

Create concise executive summaries from detailed analysis. Use when preparing board decks, executive briefings, or condensing complex analysis into decision-ready formats for senior audiences.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/executive-summary-generator

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈55 tokens for metadata: the name and description. ≈642 when used: this file. ≈2k more on demand in 3 files.

Description uses 2.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈222 characters, or 2.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Executive Summary Generator

When to use

  • A detailed analysis needs to be condensed to 1–2 pages for a senior audience
  • An executive asks "what's the bottom line?" and a full report won't be read
  • Preparing a board deck section that summarises a longer analytical workstream
  • A recurring report needs to lead with the key message rather than data tables
  • A decision needs to be made by end of day and the executive has 10 minutes

Process

  1. Extract the top 3–5 insights — go through the full analysis and identify only the findings that change or reinforce a decision. Filter out interesting-but-not-actionable findings. If you have more than 5 insights, you haven't prioritised yet.
  2. Quantify the business impact of each insight — every insight must carry a number: revenue at risk, cost saving, users affected, time to payback. Vague impact ("significant") does not belong in an executive summary. See references/executive_communication.md.
  3. Write a one-paragraph situation statement — explain why this analysis was done, what the question was, and why the timing matters. One paragraph, no jargon.
  4. Apply the pyramid principle — lead each insight with the conclusion ("Mobile churn is causing $800K ARR loss"), then the evidence, then the supporting detail. Never bury the finding at the end of a paragraph.
  5. State recommendations as specific actions — each recommendation must name what to do, who is responsible, what the expected outcome is, and by when. "Improve the app" is not a recommendation.
  6. Write the decision block — the final section names the explicit decision or approval the executive needs to give, the investment or resource required, the expected return, and the deadline. Use assets/executive_summary_template.md to assemble the document.

Inputs the skill needs

  • The full analysis or report to be summarised
  • Knowledge of the executive audience (role, priorities, decisions they're responsible for)
  • Quantified business impact for each major finding
  • Recommended actions already identified
  • Format constraints (one page, two pages, specific slide count)

Output

  • references/pyramid_principle_guide.md — answer-first structure, BLUF writing, how to edit a bottom-up draft into top-down
  • references/executive_communication.md — adapting tone, removing jargon, quantifying everything, avoiding hedge language
  • assets/executive_summary_template.md — 1–2 page template: situation, key insights (with impact), recommendations (with outcomes), decision needed

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is safe. It consists entirely of markdown documentation and templates designed to guide an AI agent or user in creating concise executive summaries using the pyramid principle. No source code, external packages, network connections, or executable files are included.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/executive-summary-generator