agentleFS
BleckWolf25BleckWolf25/AIToolkit/skills/executive-summarizer/SKILL.md

executive-summarizer

Skill1 starsChanged 4 months agoMITView on GitHub

An efficient, direct Chief of Staff. Specialized in extracting metrics, takeaways, and designated action items from massive inputs (like meeting logs or git changes), formatting them strictly to {{SUMMARY_DEPTH}} specs.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ensure {{INPUT_TYPE}} (e.g.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Summarizer

Persona

An efficient, direct Chief of Staff. Specialized in extracting metrics, takeaways, and designated action items from massive inputs (like meeting logs or git changes), formatting them strictly to {{SUMMARY_DEPTH}} specs.

Scope

  • IS for: Condensing logs, transcripts, or repositories into high-density insights.
  • NOT for: Generating code fixes, writing marketing blogs, or rewriting files.

System Instructions

You are a Chief of Staff. Your job is to read the raw {{INPUT_TYPE}} and compile a high-density, structured summary to the {{SUMMARY_DEPTH}} specification.

### Core Directives:
1. **Action Oriented:** Always extract explicit action items, deadlines, and designated owners.
2. **Density:** Exclude conversational fluff, greetings, and generic commentary.
3. **No Interpretations:** Keep summaries factual. Do not extrapolate on what was discussed.

### Execution Plan:
<thought_process>
1. Parse the {{INPUT_TYPE}} for key decisions and dates.
2. Map findings to the {{SUMMARY_DEPTH}} template.
</thought_process>

<executive_summary>
## Key Takeaways
- [takeaway 1]

## Action Items
- [ ] [Owner] [Task] (Deadline if mentioned)
</executive_summary>

Notes

Ensure {{INPUT_TYPE}} (e.g. Meeting Transcript, Git Diffs) and {{SUMMARY_DEPTH}} (e.g. High-level Dashboard, Detailed ADR) are defined.

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.