meeting-brief
Skill1 starsChanged 26 days agoMITView on GitHub
Prepares an executive meeting brief when a leader needs context, objectives, stakeholder positions and response options.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/aibast-agents-librarytheir own version, first seen Oct 13, 2026
- thefiredev-cloud/meshvault-harnesstheir own version, first seen Oct 13, 2026
- marks97/meeting-brieftheir own version, first seen Oct 9, 2026
- youdcode/open-companytheir own version, first seen Sep 21, 2026
- robertbradley-oss/skillstheir own version, first seen Sep 12, 2026
- thefiredev-cloud/meshvault-skills-startertheir own version, first seen Jul 22, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- microsoft/aibast-agents-library★ 8same name
- robertbradley-oss/skills★ 2same name
- youdcode/open-company★ 2same name
- marks97/meeting-brief★ 0same name
- thefiredev-cloud/meshvault-harness★ 0same name
- thefiredev-cloud/meshvault-skills-starter★ 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 repository133 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- access-control-auditSkill
- ai-opportunity-scanSkill
- ai-policy-writerSkill
- annual-budget-builderSkill
- application-portfolio-mapSkill
- architecture-fit-checkSkill
- automation-backlogSkill
- benefits-realisationSkill
- board-paperSkill
- bottleneck-removalSkill
- break-even-modelSkill
- budget-variance-analystSkill
- business-continuity-plannerSkill
- business-valuationSkill
- capacity-planningSkill
- case-study-writerSkill
- cash-flow-forecastSkill
- change-adoptionSkill
- change-impactSkill
- channel-profitabilitySkill
- churn-cohort-analysisSkill
- client-handoverSkill
- client-kickoffSkill
- client-profitabilitySkill
- client-relationship-managerSkill
- closeout-packSkill
- compensation-bandsSkill
- competitor-mapperSkill
- contribution-marginSkill
- cost-structure-analystSkill
- crisis-communicationsSkill
- customer-insight-synthesiserSkill
- customer-interview-designerSkill
- customer-journey-mapSkill
- customer-segmenterSkill
- cyber-risk-assessmentSkill
- dashboard-requirements-plannerSkill
- data-lineage-mapperSkill
- data-quality-auditSkill
- decision-logSkill
- decision-memoSkill
- decision-rightsSkill
- delivery-model-selectorSkill
- demand-validatorSkill
- discount-governanceSkill
- discovery-call-facilitationSkill
- discovery-call-prepSkill
- discovery-question-designSkill
- discovery-synthesisSkill
- engagement-outcomesSkill
- evidence-synthesiserSkill
- executive-dashboardSkill
- executive-summarySkill
- fee-settingSkill
- financial-statement-diagnosticSkill
- fundraising-readinessSkill
- funnel-diagnosticSkill
- go-to-marketSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
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 9
Use before a consequential client, board, partner or governance meeting with limited preparation time.
- Distinctive: line 26
Use: Meeting Objective, Participants, Context, Stakeholder Positions, Key Messages, Difficult Questions, Boundaries, Agenda Tactics and …
“Common” is measured: kept by at least 6 in 10 of the 6 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
Meeting Brief
When to use it
Use before a consequential client, board, partner or governance meeting with limited preparation time.
What Claude needs
- client-context.md and meeting purpose
- Agenda, participants and decision rights
- Relevant history, commitments and sensitivities
- Desired outcome, boundaries and supporting evidence
Method
- Define the primary outcome and minimum acceptable outcome.
- Map participants by position, interest, influence and likely concern.
- Summarise relevant history, commitments and unresolved points.
- Develop key messages supported by concise evidence.
- Anticipate difficult questions and prepare direct responses.
- Set opening, decision moments, concessions and follow-up actions.
Output format
Use: Meeting Objective, Participants, Context, Stakeholder Positions, Key Messages, Difficult Questions, Boundaries, Agenda Tactics and Follow-up.
Quality checks
- Advice reflects known stakeholder positions, not invented motives.
- Key messages align with approved organisational positions.
- Desired decisions and boundaries are specific.
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.

