agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/executive-summary/SKILL.md

executive-summary

Skill1 starsChanged 22 days agoMITView on GitHub

Distils complex material into a concise executive summary when leaders need the conclusion, evidence and required action quickly.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for plans, assessments or project material that senior readers must understand without reading the full source.

    line 9
  2. Distinctive:

    Use headings: Purpose, Headline, Key Findings, Implications, Recommendation and Decisions Required.

    line 25
  3. Distinctive:

    Every statement is traceable to supplied material.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Executive Summary

When to use it

Use for plans, assessments or project material that senior readers must understand without reading the full source.

What Claude needs

  • Source material and client-context.md for background
  • Intended readers and their prior knowledge
  • Decision, action or purpose of the summary
  • Length and tone constraints

Method

  1. Identify the central question, answer and intended executive action.
  2. Extract only material findings, evidence, implications and uncertainties.
  3. Group points into a MECE narrative of context, insight and response.
  4. Lead with the conclusion, then support it with ranked evidence.
  5. State decisions, owners and timing explicitly, removing detail that belongs in appendices.

Output format

Use headings: Purpose, Headline, Key Findings, Implications, Recommendation and Decisions Required. Keep each section concise and use bullets where scanning matters.

Quality checks

  • Every statement is traceable to supplied material.
  • The requested decision and next action are unmistakable.
  • Detail, repetition and unexplained jargon are removed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free