meeting-prep
Skill0 starsChanged 7 months agoMITView on GitHub
Systematic meeting preparation for 15-minute job-hunt meetings (max 1 hour prep time). Generates comprehensive prep documents with 6 unique insights (3 core + 3 extended), vulnerability sharing strategy, intelligence-extraction questions, and next-step conversion tactics. Includes meeting environment strategies (office/transit/meal), 3 must-hit points for compressed meetings.
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 9 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
QuixiAISkillweekly-review
Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week
Also in 10 projects that use this
- +1 more from QuixiAI
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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- application-trackerSkill
- applySkill
- cold-outreachSkill
- company-deep-diveSkill
- contact-populationSkill
- job-searchSkill
- onboard-userSkill
- resume-tailorSkill
- session-checkpointSkill
- session-endSkill
- session-startSkill
- warm-followupSkill
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
- Distinctive: line 43
Read the outreach message file.
- Distinctive: line 54
If major news: update opening hook to reference it.
- Very specific: line 94
Use operating-procedures/QUICK-INSIGHT-DEVELOPMENT-GUIDE.md for the 15-minute process.
“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
Automated meeting preparation system optimised for 15-minute meetings with max 1-hour prep time.
What This Skill Does
- Comprehensive research — outreach message review, LinkedIn profiles, company news
- Insight development — 6 insights (3 core + 3 extended)
- 3 must-hit points — 30-second versions for compressed meetings
- Vulnerability strategy — prepare authentic challenges to share
- Intelligence extraction — 10+ questions to learn more than you share
- Environment strategies — office / transit / meal
- Next-step conversion — get specific commitments, not vague "let's connect"
- Prep document — complete markdown file with research and strategies
Prerequisites
- Outreach message file at
outreach/{user-slug}/messages/[company]-[person].md - Operating procedures at
operating-procedures/
MCP tools:
WebSearch(research and news checking)WebFetch(LinkedIn profiles, company pages)
Quick Start
"Prepare meeting with Jane Smith from Acme Renewables"
"Prepare meeting prep for Bob Jones — Initech, meeting Tuesday 2pm"Complete Workflow
Step 1: Review outreach message (~5 min)
- Read the outreach message file.
- Extract: insights you promised, value proposition you offered, what they might ask about.
- Note any specific hooks or angles used.
Step 2: Pre-meeting news check (~5 min)
CRITICAL — check 24 hours before meeting for breaking news:
WebSearch("[Company] latest news today OR yesterday")If major news: update opening hook to reference it.
Step 3: Research batch (~30 min)
Single research session (batch approach):
WebSearch("[Person Name] LinkedIn")
WebSearch("[Company] recent news <current and prior year>")
WebSearch("[Company] [target region] expansion")
WebSearch("[Company] [specific initiative from news]")
WebSearch("[Industry] [target region] challenges failures")
WebSearch("[Competitor] [similar initiative] lessons learned")Research focus:
- Person's recent LinkedIn activity (last 30 days)
- Company news (last 30 days)
- Competitive intelligence (who they fear, what others failed at)
- Industry patterns (what typically goes wrong)
- Regional precedents (what worked / failed in target region)
Step 4: Develop 6 insights (~20 min)
Core 3 (must deliver) — even if cut to 5 minutes.
For each insight:
- 30-second version (ultra-concise for time pressure)
- Full version (complete with evidence)
- Vulnerability bridge (your related challenge — pull from
applications/resumes/data/{user-slug}/master-experience.yamlflagged challenge bullets) - Extraction question (test their understanding)
- If resonates, go deeper (extended talking points)
Extended 3 — prepared but not essential, for when meeting extends to 30+ minutes.
Insight development process:
- Their public goal (what they announced)
- Hidden challenge (what will actually be hard)
- Pattern (similar companies that faced this)
- Counter-intuitive truth (what most get wrong)
Use operating-procedures/QUICK-INSIGHT-DEVELOPMENT-GUIDE.md for the 15-minute process.
Step 5: Prepare vulnerability shares (~5 min)
Identify 2-3 authentic challenges from the user's resume YAML (look for bullets tagged challenge_story or lesson_learned in master-experience.yaml).
Examples (illustrative — generate from user's actual experience):
- "[Past employer]'s [region] expansion was harder than expected — the talent wasn't there."
- "[Project] taught me stakeholder alignment takes 3x longer than the work."
- "At [startup], we learned 90-day adoption windows are fantasy in enterprise."
Timing: share AFTER they reveal a challenge, not before.
Step 6: Create intelligence-extraction plan (~5 min)
Must-learn items:
- Actual constraints (people, money, time, politics)
- Real timeline (not the public version)
- Decision process (who, how, when)
- Competition concerns (who they fear)
- Success metrics (how they're measured)
Question categories:
- Constraint: "What's constraining growth right now?"
- Surprise: "What's been the biggest surprise so far?"
- Competition: "How do you see the competitive landscape?"
- Timeline: "What needs to happen in the next 90 days?"
- Stakeholder: "Who else needs to be convinced?"
Golden question: "What keeps you up at night about this?"
Step 7: Generate prep document (~10 min)
Output: outreach/{user-slug}/prep/[company]-[person]-prep.md
# Meeting Prep: [Person Name] - [Company Name]
**Meeting Date**: [Date/Time] | **Duration**: 15 minutes | **Format**: [Office/Video/Transit/Meal]
**Prepared**: [Date] | **Last News Check**: [Date/Time]
---
## 3 Must-Hit Points (If Meeting Cut Short)
1. [30-second version of best insight]
2. [30-second version of second insight]
3. [30-second version of third insight]
---
## Meeting Environment Strategy
**Setting**: [Office/Video/Transit/Meal]
**Approach**: [Specific strategy]
**Materials**: [What you can/cannot use]
**Delivery Style**: [Formal/Conversational/Story-based]
---
## Quick Reference (2-Minute Scan)
### What [Company] Does
[1-2 sentences]
### Person Overview
- **Role**: [Title] (since [Date])
- **Recent Win**: [Achievement]
- **Strategic Focus**: [Priorities]
### Recent Company Signals
- [Date]: [News]
### Your Outreach Hook
- [What you emphasized]
- [Value proposition]
---
## Your Unique Insights (Core 3 + Extended 3)
### PRIMARY SET (Must Deliver)
#### Insight #1: [Title]
- **30-Second Version**: [Ultra-concise]
- **Full Version**: [Complete with evidence]
- **Vulnerability Bridge**: [Your related challenge]
- **Extraction Question**: [Test understanding]
- **If Resonates**: [Extended points]
[Repeat for #2 and #3]
### EXTENDED SET (If Time Allows)
[#4, #5, #6 with same structure]
---
## Meeting Flow by Duration
### If 5 minutes (compressed)
0:00-0:30 Quick rapport
0:30-4:00 Three must-hit points
4:00-5:00 Get commitment for full discussion
### If 15 minutes (standard)
0:00-2:00 Opening & rapport
2:00-8:00 Core discussion & extraction
8:00-13:00 Deliver insights with vulnerability
13:00-15:00 Next steps with specificity
### If 30+ minutes (extended)
0:00-3:00 Deeper rapport building
3:00-10:00 Thorough challenge exploration
10:00-20:00 All 6 insights with discussion
20:00-25:00 Partnership exploration
25:00-30:00 Concrete next steps
---
## Vulnerability Moments
### Prepared Shares
1. [Challenge story]
2. [Failure learning]
3. [Humility moment]
**When to deploy**: after they share, when too theoretical, to create connection.
---
## Intelligence Extraction Plan
### Must-learn
- [ ] Constraints
- [ ] Real timeline
- [ ] Decision process
- [ ] Competition concerns
- [ ] Success metrics
- [ ] Political dynamics
### Questions
[10+ specific questions]
---
## Post-Meeting Actions
### Within 30 minutes
1. Send thank-you referencing specific moment
2. Confirm commitments
3. Share promised resources
### Within 2 hours
1. Create/send framework discussed
2. Calendar follow-up if agreed
3. Update database
---
## Next-Step Conversion
Instead of vague:
- "Let's connect again"
Get specific:
- "Can we calendar 30 minutes next Tuesday?"
- "Should I send availability for this week?"
- "Would Thursday 2pm work for a deeper dive?"
**Commitment Ladder**:
1. Best: "Let me introduce you to my team" → group call
2. Good: "Let's dive deeper next week" → calendar time
3. OK: "Send more information" → framework + follow-up time
4. Minimum: "Keep in touch" → specific check-in dateMeeting Environment Strategies
Office / video (traditional)
- Full prep with all materials
- Screen-share capability
- All 3 insights ready
- Professional backdrop
Transit / walking (busy exec)
- 3 must-hit points memorised (no notes)
- Story-based delivery
- Key numbers memorised
- Shorter, punchier insights
Meal (relationship focus)
- Defer detailed discussions
- Focus on rapport and trust
- Save technical for follow-up
- Vulnerability moments work best
Quality Checklist
Before meeting:
- Outreach message reviewed
- News check completed (24 hours before)
- 6 insights prepared
- 3 must-hit points ready
- Vulnerability shares prepared
- 10+ extraction questions ready
- Prep document created
During meeting:
- Referenced recent news
- Shared a vulnerability moment
- Extracted 3+ intelligence points
- Delivered at least 2 insights
- Got a specific next step
Reference Documentation
- Full workflow:
operating-procedures/MEETING-PREP-PROCEDURE-v4.md - Insight development:
operating-procedures/QUICK-INSIGHT-DEVELOPMENT-GUIDE.md
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.

