executive-briefing
Skill0 starsChanged 2 months agoMITView on GitHub
Turn messy source material into a concise executive briefing (500 words or fewer). For executives, founders, managers, consultants, clinicians, program leads, and operators in any industry who need to quickly understand a topic, meeting, company, market, project, or decision context. Use whenever the user says "brief me," "executive summary," "executive briefing," "decision brief," "what do I need to know," "catch me up," "prepare me for," "summarize this for a meeting," "key takeaways," "background context," "what's important here," "TL;DR," "bottom line," "prep me," "distill this," "boil this down," or "what matters here." Also trigger when the user provides articles, meeting notes, PDFs, memos, or pasted text and wants a summary for a busy reader or decision-maker — even without the word "briefing." If the user is preparing for a meeting, board session, client review, or leadership call and wants to understand background material quickly, this skill applies. Source-agnostic. Do NOT use for a full recommendation memo with evidence grading — use the decision-memo-drafter skill. Do NOT use for a single meeting transcript that needs action items and owners — use the call-transcript-followup skill.
10 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- webkubor/writing-standard-skillstheir own version, first seen Nov 1, 2026
- webkubor/talk-skillstheir own version, first seen Nov 1, 2026
- zime-ai/zime-gtm-skillstheir own version, first seen Nov 1, 2026
- ShawhinT/non-coding-skillstheir own version, first seen Oct 29, 2026
- latour-ai/skillsedited, first seen Oct 19, 2026
- ian-lawrence423/Claude-skillstheir own version, first seen Oct 11, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- latour-ai/skills★ 6987% same
Wrote their own version · 9
- anthropics/claude-agent-sdk-demos★ 2.8ksame name
- juntoku9/claude-for-crypto-research★ 106same name
- ShawhinT/non-coding-skills★ 40same name
- zime-ai/zime-gtm-skills★ 19same name
- nickstellarstreamai/ai-opportunity-finder★ 11same name
- webkubor/talk-skills★ 6same name
- webkubor/writing-standard-skills★ 6same name
- ian-lawrence423/Claude-skills★ 0same name
- m2ai-mcp-servers/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- audit-request-binderSkill
- business-one-pagerSkill
- call-notes-followupSkill
- company-first-passSkill
- conference-prep-plannerSkill
- contract-obligations-extractorSkill
- counterparty-diligenceSkill
- decision-memo-drafterSkill
- document-redline-diffSkill
- expert-interview-synthesisSkill
- hundred-day-plan-drafterSkill
- inbox-triageSkill
- intro-email-generatorSkill
- linkedin-post-generatorSkill
- marketing-claims-prescreenSkill
- market-map-builderSkill
- meeting-minutes-generatorSkill
- nda-reviewSkill
- payout-reconciliation-checkerSkill
- performance-attribution-narratorSkill
- periodic-report-synthesizerSkill
- podcast-episode-analyzerSkill
- presentation-transcript-extractorSkill
- private-company-tear-sheetSkill
- professional-profile-briefSkill
- project-folder-organizerSkill
- proposal-first-passSkill
- questionnaire-red-flag-scannerSkill
- questionnaire-response-drafterSkill
- red-team-premortemSkill
- relationship-status-summarizerSkill
- side-letter-term-extractorSkill
- skill-idea-generatorSkill
- stakeholder-update-generatorSkill
- teach-meSkill
- unit-economics-memoSkill
- watchlist-news-alertSkill
- weekly-recap-writerSkill
- workflow-to-ai-solverSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
10
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
- Distinctive: line 27
Read all available source material carefully — attachments, pasted text, linked pages, conversation context.
- Distinctive: line 33
Write the briefing in the output format below.
- Distinctive: line 37
Use this exact structure. Keep the total briefing to 500 words or fewer unless the user requests otherwise.
- Distinctive: line 59
Don't stop. Produce a lightweight version using whatever is available, then append:
- Distinctive: line 72
Write as if you're briefing a smart, busy person who respects your judgment and has zero patience for fluff.
- Distinctive: line 76
Before delivering the briefing, verify:
- Distinctive: line 80
Every factual claim traces back to the provided source material
- Distinctive: line 82
No unsupported recommendations or speculation
- Distinctive: line 84
No generic filler sentences that could appear in any briefing
- Distinctive: line 95
Read the proposal and the threads, note where the emails contradict or qualify the proposal, and surface the unresolved points as open …
“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.
Files
Executive Briefing
Turn messy, lengthy, or scattered source material into a concise executive briefing that a busy reader can absorb in under two minutes.
Why this skill exists
Executives, founders, managers, and operators constantly receive dense material — articles, meeting transcripts, research notes, memos, PDFs, status reports — and need the essential facts extracted and organized fast. The goal is not a generic summary. It's a briefing: neutral, thorough within its scope, and honest about what it doesn't know.
Core principle
Only include what the provided source material supports. Do not invent facts, fill in missing background from general knowledge, speculate beyond the sources, or make recommendations unless the user explicitly asks. If the source says something ambiguous, flag it as an open question rather than resolving it with assumptions.
This matters because people make decisions based on briefings. An unsupported claim presented as fact can lead to bad decisions. Err on the side of "here's what we don't know" over "here's my best guess."
How to produce the briefing
- Read all available source material carefully — attachments, pasted text, linked pages, conversation context.
- Identify the main topic, the apparent purpose, and who the briefing is for (infer from context or ask).
- Extract the most relevant facts. Relevance means: would a decision-maker preparing for a decision or meeting need this?
- Separate confirmed facts from open questions. This distinction is the backbone of a good briefing.
- Preserve important background context — history, stakeholders, prior events, market or organizational dynamics — but only what appears in the sources.
- Strip out duplication, filler, promotional language, and unsupported interpretation.
- Write the briefing in the output format below.
Output format
Use this exact structure. Keep the total briefing to 500 words or fewer unless the user requests otherwise.
**TL;DR**
2-4 sentences capturing the single most important takeaway. A reader who only sees this section should walk away informed.
**Key Facts**
- Bullet points with the most relevant facts, each grounded in the provided source material.
- Attribute or qualify where the source is ambiguous ("according to the memo," "the transcript suggests").
**Background Context**
Briefly explain what a reader needs to understand the topic — history, stakeholders, prior events, business, market, or organizational context. Only include what the sources support.
**Open Questions**
Important unresolved questions surfaced by the material. Do not answer these unless the answer is directly supported by the sources. These are genuinely open — flag them so the reader knows where the gaps are.
**Source Notes**
One or two sentences identifying what source material the briefing drew from (e.g., "Based on the attached article and meeting transcript from May 15").When context is limited
Don't stop. Produce a lightweight version using whatever is available, then append:
**Additional Context That Would Improve This Briefing**
- [List specific missing information: intended audience, the decision being made, relevant prior meetings, additional source documents, the user's objective, time sensitivity, etc.]This is more useful than refusing to produce anything. A partial briefing with clearly identified gaps is better than "I don't have enough information."
Tone
Neutral executive voice — clear, direct, thorough, and non-promotional. Avoid corporate-speak ("synergies," "leverage," "align"), generic filler ("it's worth noting that"), and unnecessary hedging. If the source material uses specialized terminology the reader would expect (clinical terms, engineering concepts, accounting terms, legal terms), keep it — but don't add jargon that isn't in the source.
Write as if you're briefing a smart, busy person who respects your judgment and has zero patience for fluff.
Quality checks
Before delivering the briefing, verify:
- Total length is 500 words or fewer (unless the user requested otherwise)
- Tone is neutral and executive-appropriate
- Every factual claim traces back to the provided source material
- Facts and open questions are clearly separated
- No unsupported recommendations or speculation
- Concise but not shallow — important nuance is preserved
- No generic filler sentences that could appear in any briefing
- A reader unfamiliar with the topic could act on this
Example prompts
"Brief me on the attached article and meeting notes. I'm meeting with the CEO tomorrow and need to understand the key facts, background context, and open questions."
In this case, read both sources, cross-reference where they overlap or conflict, and produce the briefing focused on what matters for that CEO meeting.
"Catch me up on this vendor's proposal and the three email threads about it before the procurement review."
Read the proposal and the threads, note where the emails contradict or qualify the proposal, and surface the unresolved points as open questions rather than resolving them yourself.
"TL;DR this 40-page program evaluation for the board packet."
Extract the findings the board would act on, keep the evaluator's stated caveats, and list what the evaluation itself says it could not measure.
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
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.

