meeting-prep
Skill0 starsChanged 10 days agoMITView on GitHub
Pre-meeting battle plan: a plan to win the room, not a research report. Use for "prep me for [company]", "meeting brief", or any upcoming sales meeting. Produces the win condition, a per-attendee crib sheet, landmines with counters, the plays to run, what to pin down, and the desired outcome. Grounded in the playbook so it names the plays the scorer will later grade.
57 other projects use a version of this.
Adopted by
Most recently taken up by
- goyalsandeep2k/claude-skillstheir own version, first seen Nov 16, 2026
- pnahtanoj/claude-skillstheir own version, first seen Nov 16, 2026
- BrianRWagner/ai-marketing-claude-code-skillstheir own version, first seen Nov 14, 2026
- sammollaei/law-firm-skillstheir own version, first seen Nov 8, 2026
- microsoft/cat-agent-skillstheir own version, first seen Nov 8, 2026
- ShawhinT/non-coding-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use email-digest, meeting-followup and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
QuixiAISkillemail-digest
Digest and ingest emails into memory, surfacing important threads and action items
Also in 3 projects that use this
yakatotechSkillmeeting-followup
Create meeting minutes and follow-up email from meeting notes in one workflow. Execute all post-meeting tasks at once
Also in 3 projects that use this
vivy-yiSkillsocial-listening
Use when needing to understand audience needs, monitor brand mentions, track competitor activities, discover trends, or gather market intelligence from Xiaohongshu conversations
Also in 3 projects that use this
MicrosoftSkillinbox-triage
Use this skill whenever the user asks to clean up, triage, declutter, or archive low-value Outlook inbox mail - "clean up my inbox", "triage my mail", "declutter my inbox", "sort out newsletters", "archive old resolved threads", "/inbox-triage" - to group only newsletters, auto-notifications, past-event meeting logistics, resolved threads, and redundant duplicates into reviewable move-proposals presented for per-bucket approval before any message moves. Do not use for reading mail, drafting or sending replies, deleting mail, executing moves without explicit per-bucket approval, or acting on messages from the user's manager, direct reports, active threads, flagged mail, or labelled/HR/Legal/Finance/Security senders.
Also in 8 projects that use this
refly-aiSkillzoom
Integrate with Zoom for video meetings. Use when you need to: (1) schedule Zoom meetings, (2) create instant meetings, or (3) manage meeting details and invitations programmatically.
Also in 3 projects that use this
vijpatel7Skillcold-outreach
Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.
Also in 4 projects that use this
Other versions57 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 57
- openai/plugins★ 7.8ksame name
- gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
- ShenSeanChen/waku-agent★ 2.2ksame name
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- davekilleen/Dex★ 509same name
- BrianRWagner/ai-marketing-claude-code-skills★ 454same name
- glebis/claude-skills★ 414same name
- sonichi/sutando★ 396same name
- explorium-ai/gtm-skills★ 346same name
47 more not listed
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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- call-debriefSkill
- company-contextSkill
- crm-recordsSkill
- humanize-copySkill
- pipeline-analysisSkill
- product-contextSkill
- sales-call-scorerSkill
- sales-intakeSkill
- sales-playbookSkill
- setupSkill
- weekly-exec-updateSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 53 edited versions we read keep these.
1
Distinctive
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
- Very specific: line 16
Read the whole deal history first: CRM description log, prior debriefs, clients/<slug>/.
- Distinctive: line 17
Check the calendar and inbox for the last 14 days.
“Common” is measured: kept by at least 6 in 10 of the 53 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 prep — the battle plan
Hard rules
- Facts about the company and attendees come from enrichment, their site, the CRM and past calls. Never from memory. An unconfirmed fact is cut, not hedged.
- Read the whole deal history first: CRM description log, prior debriefs,
clients/<slug>/. - Check the calendar and inbox for the last 14 days. The CRM lags.
Read first
company-context, product-context, sales-playbook, sales-call-scorer/PLAYBOOK.md.
Gather (in parallel; degrade gracefully when a source is missing)
- CRM: deal, stage, contacts with roles, description log, open tasks.
- Enrichment: company facts, each attendee's role and tenure.
- Their site: what they sell, recent news.
- Prior calls:
clients/<slug>/calls/and transcripts.
Output
MEETING: [company] — [date, time] — [stage]
WIN CONDITION: [the one outcome that makes this a win]
SETUP: two sentences on where the deal is and why this meeting matters.
ATTENDEES
- [name], [title]: likely push → how to win or deflect
LANDMINES
- [risk] → [counter]
PLAYS TO RUN (from PLAYBOOK.md, by number)
PIN DOWN: [the qualification gaps this call must close]
DO NOT: [what would lose the room]
PREP TO-DO: [owner, item]Quality bar
A rep should be able to read it in two minutes in the hallway and walk in knowing the one thing they must leave with.
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.

