meeting-prep
Skill4 starsChanged 36 days agoMITView on GitHub
Prepare a full briefing package for a client meeting, stakeholder call, or steering committee, with agenda, key messages, tough questions, a pre-meeting checklist, and a follow-up email draft. Use when planning or preparing for any meeting. Usage - /meeting-prep describe the meeting
58 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
- andrerodriguesops/gtm-enginetheir own version, first seen Nov 15, 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
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 versions58 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 58
- 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-skills★ 456same name
- BrianRWagner/ai-marketing-claude-code-skills★ 454same name
- glebis/claude-skills★ 414same name
- sonichi/sutando★ 396same name
48 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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-requestSkill
- code-review-lightSkill
- deliverable-qaSkill
- exec-summarySkill
- sow-reviewSkill
- stakeholder-prepSkill
- status-commsSkill
- status-reportSkill
- transcript-actionsSkill
- weekly-briefSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 54 edited versions we read keep these.
2
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 13
If not already provided in $ARGUMENTS or the conversation, ask for:
- Distinctive: line 21
If relevant project files are available (status data, the last meeting's notes, the SOW), read them to inform the preparation.
- Distinctive: line 61
After the prep package, produce a ready-to-edit follow-up email:
“Common” is measured: kept by at least 6 in 10 of the 54 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
Prepare the user for an upcoming meeting by generating a structured briefing package. The meeting itself is theirs; this package gets them ready for it.
Step 1: Gather Context
If not already provided in $ARGUMENTS or the conversation, ask for:
- Who is attending (names, roles, and their primary concerns or priorities)
- The meeting purpose (status update, decision point, escalation, discovery, and so on)
- Current project status and any recent developments the attendees may not be aware of
- What the user needs from this meeting (a decision, an approval, a commitment, information)
- Any sensitivities, history, or political dynamics to be aware of
If relevant project files are available (status data, the last meeting's notes, the SOW), read them to inform the preparation. Say which files you read.
Step 2: Produce the Meeting Prep Package
Meeting Brief
Meeting: [Meeting name / call type] Date/Time: [If provided] Attendees: [Names and roles] Objective: [One sentence: what a successful meeting looks like]
Agenda (with time allocations)
| Time | Topic | Lead | Goal |
Key Messages
For each agenda item, 2 to 3 crisp talking points. Lead with the bottom line; follow with supporting evidence. Tailor to the stated audience; C-suite language differs from working-team language.
Anticipated Questions & Tough Topics
| Likely Question | Recommended Response | Notes |
Focus on the hard questions, not the easy ones. For sensitive topics, prepare both the direct answer and a bridging statement if the conversation needs to be redirected.
What You Need from Them
Be explicit about decisions, approvals, or commitments being sought. Bring three options whenever asking for a decision; it is easier to choose than to create from scratch.
Pre-Meeting Checklist
- Relevant documents shared with attendees in advance
- Key data points confirmed and up to date
- Any follow-ups from last meeting addressed or flagged
- Technology and logistics confirmed (dial-in, room, slides)
Step 3: Draft Follow-Up Email
After the prep package, produce a ready-to-edit follow-up email:
Subject: [Meeting topic]: Summary and Next Steps
[Opening sentence] [Key decisions and agreements, 3 to 5 bullets] [Action items table: Action | Owner | Due Date] [Next touchpoint / closing]
This is a draft written before the meeting. The user rewrites it afterward to reflect what was actually decided. Never present it as a record of the meeting.
Tone
Professional and direct. For executive meetings, lead with the bottom line; senior audiences read the opening statement of each section and scan the rest.
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.

