Meeting Prep
gnekt/My-Brain-Is-Full-Crew
Prepare a comprehensive brief for an upcoming meeting. An agent skill from gnekt/My-Brain-Is-Full-Crew.
Generate a pre-meeting briefing dashboard before a call, or process post-meeting notes into a follow-up email and action items.
Install Meeting Prep
$ npx skills add TheCraigHewitt/skills --skill meeting-prep -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills meeting-prep --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cowork/meeting-prep .claude/skills/meeting-prep && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "meeting-prep" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/meeting-prep into .claude/skills/meeting-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-prep", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/cowork/meeting-prepType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill meeting-prep -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills meeting-prep --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cowork/meeting-prep .agents/skills/meeting-prep && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meeting-prep" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/meeting-prep into .agents/skills/meeting-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-prep", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill meeting-prep -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills meeting-prep --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cowork/meeting-prep .cursor/skills/meeting-prep && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "meeting-prep" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/meeting-prep into .cursor/skills/meeting-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-prep", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path cowork/meeting-prep--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill meeting-prep -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills meeting-prep --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cowork/meeting-prep .gemini/skills/meeting-prep && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "meeting-prep" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/meeting-prep into .gemini/skills/meeting-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-prep", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills meeting-prepInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill meeting-prep -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/cowork/meeting-prep .github/skills/meeting-prep && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "meeting-prep" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/meeting-prep into .github/skills/meeting-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-prep", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill meeting-prep -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills meeting-prep --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cowork/meeting-prep .opencode/skills/meeting-prep && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "meeting-prep" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/cowork/meeting-prep into .opencode/skills/meeting-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-prep", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
meeting-prep- GitHub stars
- 159
- Token cost
- ~1.4k tokens
- SKILL.md length
- 742 words
- Files
- 2
- Skills in repo
- 65
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate a pre-meeting briefing dashboard before a call, or process post-meeting notes into a follow-up email and action items.
- Works in 5 steps: Who's the meeting with? (Name, role,… → What's it about? → What outcome do you want? → …
- Says prep me for a meeting
- SKILL.md covers Determine mode, Mode: Prep, Mode: Debrief and Rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Meeting Prep is an agent skill from TheCraigHewitt/skills. Generate a pre-meeting briefing dashboard before a call, or process post-meeting notes into a follow-up email and action items. Use this whenever the user says 'prep me for a meeting,' 'I have a call with,' 'meeting with [name],' 'debrief this meeting,' 'write a follow-up,' 'process these notes,' 'action items from,' or mentions an upcoming or just-finished meeting. Works for sales calls, investor meetings, podcast appearances, partner calls, team meetings, board meetings. Outputs an interactive HTML briefing for…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
It sits in Productivity & Automation, covering Sales call preparation, Meeting notes and agendas and HTML artifacts. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
When your agent uses it
- Says prep me for a meeting
- I have a call with
- Meeting with [name]
- Debrief this meeting
Example prompts
- “prep me for a meeting,”
- “I have a call with,”
- “meeting with [name],”
- “/meeting-prep”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Who's the meeting with? (Name, role, company)
- What's it about?
- What outcome do you want?
- Any history? (Prior conversations, existing relationship)
- Meeting type? (Sales / investor / team / partner / podcast / board)
What it can do on your machine
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Meeting Prep loads about 1.4k tokens when it runs. Until then it costs about 152 tokens; SKILL.md has 742 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 742 words, ~1,435 tokens.
Download SKILL.mdSave it as
.claude/skills/meeting-prep/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- meeting-prep
- description
- Generate a pre-meeting briefing dashboard before a call, or process post-meeting notes into a follow-up email and action items. Use this whenever the user says 'prep me for a meeting,' 'I have a call with,' 'meeting with [name],' 'debrief this meeting,' 'write a follow-up,' 'process these notes,' 'action items from,' or mentions an upcoming or just-finished meeting. Works for sales calls, investor meetings, podcast appearances, partner calls, team meetings, board meetings. Outputs an interactive HTML briefing for prep mode or a clean markdown debrief + ready-to-send email for debrief mode.
Meeting Prep
You help the user walk into meetings sharper than everyone else in the room, and walk out with the follow-up email sent before they've closed their laptop.
This skill has two modes: prep (before the meeting) and debrief (after).
Determine mode
If the user mentions an upcoming meeting → prep mode. If the user mentions notes, outcomes, what was discussed → debrief mode. If ambiguous, ask: "Prepping for this one or processing it after?"
Mode: Prep
Gather context
Ask conversationally, not as a form:
- Who's the meeting with? (Name, role, company)
- What's it about?
- What outcome do you want?
- Any history? (Prior conversations, existing relationship)
- Meeting type? (Sales / investor / team / partner / podcast / board)
If a calendar connector is available, look up the event and infer what you can before asking. Skip questions you can already answer.
Research
In parallel:
- Look up the person's company (website, news, recent funding)
- Look up the person (LinkedIn-style basics, recent public activity)
- Search past emails with this person if Gmail connector is available
- Check if the user has a
BUSINESS_CONTEXT.md— use it to make goals and questions specific to the user's actual business, not generic
Produce the briefing dashboard
Save as meeting-prep-[name]-YYYY-MM-DD.html. One scannable page, designed to be read in 90 seconds.
Sections:
- Top strip — name, role, company, meeting time, location/link, your one-sentence read on what this meeting is really about
- Who they are — bio paragraph, what their company does, recent signals (funding, news, hires, posts)
- What you want from this meeting
- Primary outcome (what success looks like)
- Secondary outcome (what you'd settle for)
- Information only this person can give you
- What they probably want
- What they're likely after
- What they might ask that you should be ready for
- 5 questions to ask — lead with the sharpest. Mix: 2 information-gathering, 2 relationship, 1 that advances the deal/conversation. No softballs.
- Watch for — signals this is going well or badly. Topics to steer toward or away from. The one thing not to say.
- Suggested agenda — proposed time allocation if you're driving the meeting
Meeting-type additions
Sales / biz dev — likely objections + responses, BANT-style qualification checklist, the next step to propose
Investor — numbers to have memorized (ARR, growth, burn, runway, churn), the narrative (why now, why you), questions investors ask that founders fumble
Podcast — 3 stories from your experience relevant to the topic, your contrarian or surprising take, a natural one-liner about your business
Team / internal — is this a decision meeting or info meeting? what decision should it produce? who shouldn't be there?
Partner — mutual benefit framing, what you can offer them, what would make a partnership meaningful enough to pursue
Mode: Debrief
Show full SKILL.md (296 more words)Show less
Gather the notes
Ask the user to paste or describe what happened. Accept any format — rough notes, transcript, voice memo transcription, bullets.
Produce two artifacts
1. meeting-debrief-[name]-YYYY-MM-DD.md — clean markdown debrief:
- Summary (3–5 bullets, no filler)
- Decisions made — what was decided and why
- Action items table — Action | Owner | Deadline | Priority. Propose deadlines if none were discussed and flag them as proposed.
- Open questions — anything unresolved that needs to come back
- Flags — anything surprising, concerning, or worth remembering about this person for next time
2. A follow-up email draft — saved as Gmail draft if connector available, otherwise printed in chat. Structure:
- Open with one specific line of genuine appreciation (not "thanks for your time" — something concrete from the conversation)
- Summarize what was discussed in 2–3 bullets
- List agreed-upon next steps with owners
- Propose the next meeting/checkpoint if appropriate
- Close with one clear CTA
Tone by meeting type: Sales = confident, moves the deal. Investor = professional, concise, leaves them wanting more. Team = direct, action-oriented. Podcast = warm, relationship-building. Partner = collaborative, specific about mutual benefit.
Rules
- Specificity over comprehensiveness. "Ask about their priorities" is useless. "Ask what's changed since they raised their Series B in March" is useful. Use real research, real names, real numbers.
- A prep brief should take 2 minutes to read. Not 10. If it's longer, you're padding.
- The follow-up email is sacred. Sent within 15 minutes of the call ending changes how the user is perceived. Make it good enough to send with minimal editing.
- Don't over-prepare. A founder who reads 10 pages of prep sounds rehearsed. One who has 3 sharp questions and genuine curiosity sounds impressive. Choose 3 sharp things over 30 mediocre ones.
- Every debrief ends with a next step. If the notes don't include one, flag that gap explicitly.
© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in cowork/meeting-prep of TheCraigHewitt/skills.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit fdbf39b
Compare with similar skills
Meeting Prep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Meeting Prep this skillTheCraigHewitt/skills | 159 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Meeting Prepgnekt/My-Brain-Is-Full-Crew | 3.9k | — | ~2.7k | Automated safety check: Warn | Custom licence | |
| Gws Workflow Meeting Prepgoogleworkspace/cli | 31k | — | ~300 | Automated safety check: Pass | Apache-2.0 | |
| Capture Meetingkbanc85/claudia | 296 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Meeting Preptechwolf-ai/ai-first-toolkit | 132 | — | ~1k | Automated safety check: Pass | MIT | |
| Calendar Prepborghei/Claude-Skills | 891 | — | ~842 | Automated safety check: Pass | MIT |
Similar skills
Gws Workflow Meeting Prep
googleworkspace/cli
Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
Capture Meeting
kbanc85/claudia
Process meeting notes or transcript to extract decisions, commitments, and insights.
Meeting Prep
techwolf-ai/ai-first-toolkit
Comprehensive pre-meeting briefing that gathers all relevant context from Slack, email, Google Docs, Notion, and calendar.
Calendar Prep
borghei/Claude-Skills
Generate one-page meeting briefings from structured input (attendees, prior context, decisions needed).
Handwriting Stand Up
limin112/min-skill
Turn a screen recording of handwriting (or a photo of handwritten text) into a single-file HTML "continuation" — the recording plays, the ink lifts off the page as solid 3D letters, a short animated…
More from TheCraigHewitt/skills
All 65 skills in this repoCarousels
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
Audience Research
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
Brain Dump
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
Channel Audit
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
Channel Strategy
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
Cold Call
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Related
Categories
Questions about Meeting Prep
What does Meeting Prep do?
Generate a pre-meeting briefing dashboard before a call, or process post-meeting notes into a follow-up email and action items. Meeting Prep is an agent skill from TheCraigHewitt/skills. Generate a pre-meeting briefing dashboard before a call, or process post-meeting notes into a follow-up email and action items.
When should I use Meeting Prep?
Meeting Prep fits situations like: says prep me for a meeting; I have a call with; meeting with [name]; debrief this meeting.
How do I install Meeting Prep in Claude Code?
Run `npx skills add TheCraigHewitt/skills --skill meeting-prep -a claude-code`. Or copy the skill folder (cowork/meeting-prep in TheCraigHewitt/skills) into .claude/skills/meeting-prep in your project. Claude Code loads it when a task matches its description.
How do I install Meeting Prep in Codex?
Run `npx skills add TheCraigHewitt/skills --skill meeting-prep -a codex`. Or copy the skill folder (cowork/meeting-prep in TheCraigHewitt/skills) into .agents/skills/meeting-prep in your project. Codex loads it when a task matches its description.
Can I use Meeting Prep in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill meeting-prep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meeting-prep, .gemini/skills/meeting-prep, .github/skills/meeting-prep and .opencode/skills/meeting-prep in your project.
What does Meeting Prep need to run?
SKILL.md names no scripts, command-line tools or credentials: Meeting Prep is instructions for the agent only.
Does Meeting Prep access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Meeting Prep safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Meeting Prep use?
Meeting Prep is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Meeting Prep use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Meeting Prep?
Skills that share tags, products or a category with Meeting Prep: Meeting Prep (gnekt/My-Brain-Is-Full-Crew, 3.9k stars), Gws Workflow Meeting Prep (googleworkspace/cli, 31k stars), Capture Meeting (kbanc85/claudia, 296 stars) and Meeting Prep (techwolf-ai/ai-first-toolkit, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Meeting Prep?
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.