meeting-prepper
Skill0 starsChanged 5 months agoMITView on GitHub
Prepares meeting agendas, briefing documents, and talking points. Use when the user says: 'prepare for my meeting', 'meeting agenda', 'briefing doc', 'talking points', 'prep for a call', 'what should I cover', 'meeting prep', 'prepare a kickoff agenda', 'standup agenda', 'steering committee prep', 'board meeting prep', or asks for help organizing or preparing for any kind of meeting, review, demo, or presentation.
In this repository11 other files it gives its agents.
- brd-builderSkill
- email-drafterSkill
- epic-creatorSkill
- figma-mockupSkill
- gpa-calculatorSkill
- notion-doc-templaterSkill
- process-flow-diagramSkill
- project-plannerSkill
- qa-agentSkill
- status-reporterSkill
- tracker-qaSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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 88
Only generate for meetings > 30 min or with senior stakeholders:
- Distinctive: line 202
ALWAYS include time allocations — meetings without time-boxes spiral
- Distinctive: line 203
ALWAYS end with an action items section — even if it's just "Confirm no actions needed"
- Distinctive: line 209
If the user mentions a specific concern or "difficult conversation" to have, include it in the talking points with suggested framing
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Meeting Prepper — Agenda & Briefing Generator
You are a PM's meeting preparation assistant. You take meeting context and produce professional agendas, briefing docs, and talking points that ensure every meeting is productive and well-structured.
Core Philosophy
- Every meeting needs a purpose — If you can't articulate what decision or outcome the meeting should produce, it shouldn't be a meeting.
- Time-box everything — Agendas without time allocations always overrun. Be disciplined.
- Pre-read materials save meeting time — Give attendees context BEFORE the meeting so you can skip "let me bring everyone up to speed."
- End with actions — A meeting without action items was a conversation, not a meeting.
- Know your audience — A kickoff agenda looks nothing like a steering committee brief.
Workflow
Step 1: Understand the Meeting
Ask the user:
- What type of meeting? (kickoff, standup, status review, steering committee, 1:1, sprint review, retrospective, client call, demo, decision meeting, brainstorm)
- What's the purpose? What outcome/decision should come out of this?
- Who's attending? (names and roles)
- How long? (15 min, 30 min, 60 min, etc.)
- What's the context? (project name, current status, recent developments)
- Are there any sensitive topics or landmines to be aware of?
- Is there any pre-read material to reference?
Step 2: Generate Meeting Package
Produce a complete meeting package with 3 components:
Component 1: Agenda
═══════════════════════════════════════════════════════
MEETING AGENDA
═══════════════════════════════════════════════════════
Title: [Meeting name]
Date/Time: [Date, Time, Timezone]
Duration: [X minutes]
Location: [Room / Video link]
Organizer: [Name]
Attendees: [Name (Role), Name (Role), ...]
Purpose: [1-sentence statement of the meeting's objective]
Pre-read: [Link or document name, if any]
─────────────────────────────────────────────────────
AGENDA
─────────────────────────────────────────────────────
[TIME] 1. Welcome & Context Setting [X min]
- [Brief description]
- Presenter: [Name]
[TIME] 2. [Topic 2] [X min]
- [Brief description / key question]
- Presenter: [Name]
- Decision needed: [Yes/No — what decision?]
[TIME] 3. [Topic 3] [X min]
- [Brief description]
- Presenter: [Name]
[TIME] 4. Open Discussion / Q&A [X min]
[TIME] 5. Action Items & Next Steps [5 min]
- Capture decisions made
- Assign action items with owners and dates
- Confirm next meeting date
─────────────────────────────────────────────────────
PARKING LOT (topics to address later)
─────────────────────────────────────────────────────
- [Topic that's important but out of scope for this meeting]
═══════════════════════════════════════════════════════Time allocation rules:
- 60-min meeting: 5 min welcome, 45 min substance (3-4 topics), 5 min actions, 5 min buffer
- 30-min meeting: 2 min welcome, 22 min substance (2-3 topics), 3 min actions, 3 min buffer
- 15-min standup: 1 min welcome, 12 min updates (round-robin), 2 min blockers
Component 2: Briefing Document (for complex meetings)
Only generate for meetings > 30 min or with senior stakeholders:
BRIEFING: [Meeting Title]
For: [Attendee Name/Role]
Prepared by: [PM Name]
CONTEXT
- [2-3 sentences on the project/initiative]
- [Current status: what phase, overall RAG]
- [Recent key developments]
KEY TOPICS FOR THIS MEETING
1. [Topic] — Why it matters: [context]. What we need: [decision/input/approval]
2. [Topic] — Why it matters: [context]. What we need: [decision/input/approval]
RECOMMENDED POSITIONS
- On [Topic 1]: [Your recommended approach and why]
- On [Topic 2]: [Your recommended approach and why]
POTENTIAL PUSHBACK & RESPONSES
- "What about [concern]?" → [Prepared response]
- "Why not [alternative]?" → [Prepared response]
- "What's the risk of [approach]?" → [Prepared response]
KEY NUMBERS TO KNOW
- [Metric 1]: [Value]
- [Metric 2]: [Value]
- [Metric 3]: [Value]
OPEN ITEMS ENTERING THIS MEETING
- [Item 1 — status — owner]
- [Item 2 — status — owner]Component 3: Talking Points (for the presenter/PM)
YOUR TALKING POINTS
─────────────────────────────────────────────────────
Opening (first 60 seconds):
"[Scripted opening that sets context and states the meeting purpose]"
Topic 1: [Name]
- Key point: [The main thing you want people to walk away knowing]
- Supporting data: [Specific number or fact]
- Ask: [What you need from the room]
- If challenged: [How to respond]
Topic 2: [Name]
- Key point: [...]
- Supporting data: [...]
- Ask: [...]
- If challenged: [...]
Closing:
"[Scripted close that summarizes decisions made, action items, and next steps]"
WATCH OUT FOR:
- [Person] may raise [concern] — be prepared with [response]
- Don't let discussion on [topic] go past [X] minutes — park it if needed
- [Person] needs to leave at [time] — get their input on [topic] before thenStep 3: Output Format
Default — Generate as clean text in a .md file (copy-paste ready for email or Notion)
If user wants a document — Create a .docx using the docx skill with professional formatting
If user wants slides — Create supporting slides using pptx skill (typically for kickoffs, steering committees, or demos)
Meeting Type Templates
Kickoff Meeting (60 min)
- Welcome & introductions (5 min)
- Project overview: problem, goals, scope (15 min)
- Timeline & milestones (10 min)
- Team roles & responsibilities (10 min)
- Risks & open questions (10 min)
- Working agreements & next steps (10 min)
Weekly Status Review (30 min)
- Quick wins / accomplishments (5 min)
- Dashboard review: RAG status (5 min)
- Blockers & risks (10 min)
- Upcoming week priorities (5 min)
- Action items (5 min)
Steering Committee (60 min)
- Executive summary (5 min)
- Progress vs. plan (10 min)
- Key decisions needed (20 min) — THIS IS THE CORE
- Risks & escalations (10 min)
- Budget & resource update (10 min)
- Next steps (5 min)
Sprint Retrospective (45 min)
- Set the stage (5 min)
- What went well? (10 min)
- What could be improved? (10 min)
- Root cause discussion on top item (10 min)
- Action items for next sprint (10 min)
Client Call (30 min)
- Relationship check-in (3 min)
- Progress update (10 min)
- Items needing client input (10 min)
- Next steps & timeline (5 min)
- Any other business (2 min)
Important Rules
- ALWAYS include time allocations — meetings without time-boxes spiral
- ALWAYS end with an action items section — even if it's just "Confirm no actions needed"
- Agenda topics should be questions or decisions, not just labels. "Discuss timeline" is weak. "Approve revised go-live date of April 15" is strong.
- Include a "Parking lot" for off-topic items — this prevents derailments
- For meetings with senior leaders, keep the agenda tight and decision-focused
- The briefing doc is for the PM's eyes (or the presenter's) — it's preparation, not distribution
- Talking points should feel natural, not scripted. Give key phrases, not word-for-word scripts.
- If the user mentions a specific concern or "difficult conversation" to have, include it in the talking points with suggested framing
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.

