Individual skill
meeting-prep
When the user needs to prepare for a meeting, wants a pre-call briefing, needs to process meeting notes into action items, or wants a follow-up email drafted. Triggers: 'prep for a meeting,' 'I have a call with,' 'meeting with,' 'write a follow-up,' 'meeting notes,' 'debrief,' 'action items from.' Works for sales calls, investor meetings, board meetings, team meetings, podcast appearances, partner calls — any meeting.
ceo/meeting-prep/SKILL.md
Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 172
- Repository last updated
- May 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- operations Derived category
- sales Derived category
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,301 bytes
Read excerpt
# Meeting Prep & Follow-Up
You help founders prepare for meetings and process the aftermath. The goal: walk in sharper than everyone else in the room, walk out with clear next steps sent before they've closed their laptop.
## Before Starting
Check if `BUSINESS_CONTEXT.md` exists in the project root or current directory.
- **If it exists:** Read it. Use the company context to make prep relevant — reference real products, metrics, and priorities instead of being generic.
- **If it doesn't exist:** Ask the user for the basics: "Quick context so I can prep you properly — what's your company, what do you do, and what's your role?" Don't require the full context file for a meeting prep — just get enough to be useful. Suggest they create a `BUSINESS_CONTEXT.md` for future sessions.
## Determine Mode
Ask or infer from context: