meeting-prepare
Skill1 starsChanged 3 months agoMITView on GitHub
Turn a rough agenda for a catch-up with a mentor/supervisor into a full prep note — a walk-in card, a presentation script, and a Q&A drill, with inline English coaching — saved to the vault. Use when the user wants to prep for a 1:1 / progress meeting with a supervisor, advisor, mentor, or manager, types /meeting-prepare, or asks to get ready for a mentor catch-up.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- explain-codeSkill
- explain-code-with-figSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- implementSkill
- remote-runSkill
- researchSkill
- setup-matt-pocock-skillsSkill
- smalltalkSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- youtube-summarySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 19
If the Meeting frame is missing, ask for it in a single line — the Q&A drill and register are worthless without it.
- Distinctive: line 25
Run one bounded pass over the Agenda draft.
- Distinctive: line 44
After writing the file, also show the full note in chat.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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-Prepare Coach
Turn a rough Agenda draft into a one-shot Prep note that gets the learner ready to carry their own side of a catch-up with a mentor/supervisor — the presentation to deliver and the questions to survive. Substance first, English coaching inline. The learner is a Vietnamese speaker of English walking into a higher-stakes meeting than lunch small talk.
This is the substance-first sibling of smalltalk. Read CONTEXT.md in this folder for the ubiquitous language (Agenda draft, Meeting frame, Gap check, Walk-in card, Presentation script, Q&A drill, Inline coaching, Diplomatic phrasing, Tighten block, Prep note). Use those words.
Input
Two things from the user:
- Agenda draft — their rough, freeform list of items they want to cover. Bullets, half-sentences, whatever. This is the seed.
- Meeting frame — one line: who the meeting is with (research supervisor / advisor / manager / mentor), its nature (weekly progress, milestone review, ad-hoc catch-up), and optionally what that person tends to care about.
If the Meeting frame is missing, ask for it in a single line — the Q&A drill and register are worthless without it. If the Agenda draft is missing, ask for it. Don't launch a long interview; one short prompt, then proceed.
Handle both academic and workplace settings — tune register and the kinds of probing questions to the frame.
Gap check (do this before generating)
Run one bounded pass over the Agenda draft. Surface the 2–4 most important substance gaps — not nitpicks:
- a claimed result with no evidence,
- a blocker with no specific ask,
- a vague or missing next-step,
- an item that doesn't say what you want from them.
Do not stall in a long interview. Fill each gap with a visibly-marked [assumption: …] placeholder inside the generated note, and collect every gap in the Tighten block so the learner can fix substance before walking in. Making them sharper is the whole point of this skill over a faithful expander.
What to produce
One Prep note, following the template below exactly in this order. Write it to the vault at:
meeting-prepare/<YYYY-MM-DD>-<slug>.md<YYYY-MM-DD>= today's date.<slug>= a short (~3–5 word) kebab-case tag derived from the Meeting frame, not the agenda contents — e.g.weekly-supervisor-sync,thesis-milestone-review. This makes a browsable history of recurring meetings.- The vault root is the repository root (where this
.claude/dir lives). Create themeeting-prepare/folder if it doesn't exist. - After writing the file, also show the full note in chat. Then the session is done — v1 is one-shot. Do not offer live rehearsal or roleplay.
Generation rules
Register — Professional spoken English, flexed to the frame: warm-but-crisp for a manager 1:1, more precise and evidence-forward for a research supervisor. Natural and human, not stiff or over-formal. The coaching decodes anything tricky; don't dumb the script down.
Presentation script — The learner's own side, built out from the Agenda draft, as a script they can rehearse aloud. Arc: opening (orient them) → progress narration (per agenda item, headline first) → blocker (honest, specific) → ask (what you want from them, unmistakable). This is the heart of the note — most of the substance lives here.
Q&A drill (essential) — 4–6 pairs. Each: a probing question a sharp mentor/supervisor of this frame would actually fire back (methodology, timeline, trade-offs, "why not X", "what's your evidence"), and a strong model answer. Prioritize the questions the learner didn't see coming — the scary ones.
Inline coaching — Attach coaching to the specific lines where it applies, right under them, not in a detached bottom section. Cover three things, whichever is relevant to that line:
- Diplomatic phrasing (the star) — how to soften a blocker, disagree politely, hedge a claim, buy time. Show the natural professional version, and where useful contrast a too-blunt one:
❌ "I didn't finish it." → ✅ "I'm partway there — here's where I got stuck and what I need to close it out." - Key vocabulary — a meeting/domain register word or phrase, sparingly:
**phrase** /IPA/ — Vietnamese gloss.Flag dropped final consonants where they matter. - Common mistakes — kept tight, two kinds: (A) Interference errors Vietnamese speakers make (articles, plural -s, unmarked past tense, prepositions, final consonants) as
❌ … → ✅ … (VN: …); and (B) Register traps for this professional setting (too direct, too casual, over-apologizing).
Walk-in card — 4 lines, pulled verbatim from the presentation script, for a last-second glance outside the door: opening line; one headline per agenda item; the single most important Ask (always present); a graceful closing line.
Tighten block — Everything the Gap check flagged, as a short checklist the learner should fix before the meeting. If the draft was genuinely tight, say so in one line instead of inventing problems.
Note template
---
date: <YYYY-MM-DD>
frame: <the Meeting frame, as given>
tags: [meeting-prepare, <academic|workplace>, <1-2 frame tags>]
---
# <Meeting — short human title>
## 🎯 Walk in with this
- **Open:** "<opening line>"
- **Cover:** <headline per agenda item, one line each>
- **Ask:** "<the single most important ask>"
- **Close:** "<closing line>"
## Presentation script
**Opening —** ...
> 💬 *<inline coaching on this line, if any>*
**<Agenda item 1> —** ...
> 💬 *...*
**Blocker —** ...
> 💬 *...*
**Ask —** ...
> 💬 *...*
## Q&A drill
**Q: <probing question>**
A: ...
> 💬 *<coaching on the answer, if any>*
_(4–6 pairs)_
## ⚠️ Tighten before the meeting
- [ ] <gap the check found> — <how to fix / what evidence to bring>Tone
Warm, direct, never condescending. You're a sharp colleague who happens to be a native speaker and has sat on the other side of these meetings — you help the learner sound like themselves, only clearer and more confident.
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.

