/meeting-prep
Prep me for a meeting or call — who I'm meeting, background, talking points. Use for "prep me for", "get me ready for", "what should I know before", "who am I meeting", "brief me on my call with".
$ npx -y skills add ShenSeanChen/waku-agent --skill meeting-prep --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/meeting-prep
Context preview
The summary Claude sees to decide when to auto-load this skill.
Prep me for a meeting or call — who I'm meeting, background, talking points. Use for "prep me for", "get me ready for", "what should I know before", "who am I meeting", "brief me on my call with".
SKILL.md
meeting-prep.SKILL.mdname: meeting-prep
description: Prep me for a meeting or call — who I'm meeting, background, talking points. Use for "prep me for", "get me ready for", "what should I know before", "who am I meeting", "brief me on my call with".
How to prep
1. Find the meeting: call `list_events` and pick the one that matches the name or time the user gave. Note the title, time, attendees, and notes. 2. Pull what memory knows about each attendee — who they are, past conversations, preferences, anything promised and not yet delivered. This is the heart of the prep: the goal is walking in like you remember everything. 3. If the attendee or their company is public-facing and memory is thin, one `search_web` for recent news. Skip this for personal meetings — coffee with a friend doesn't need a briefing document. 4. Write the prep card (format below), then offer to `save_note` it so it's there to glance at on the way in.
The prep card
- **When** — one line: time, duration, where/how.
- **Who** — 2-3 lines per attendee: relationship, last interaction, open
threads (anything owed in either direction).
- **Why now** — the agenda from the event notes, plus anything memory says
is unresolved with this person.
- **Three talking points** — concrete, memory first, web second. "Ask how
the Berlin launch went" beats "discuss recent developments".
Keep it skimmable — it gets read in the elevator, not at a desk.
Edge cases
| Situation | Do | |---|---| | No matching event on the calendar | Say so, then prep from the name alone using memory and web | | Several events match | Prep the next upcoming one; list the others in one line | | Memory knows nothing about the attendee | Say that plainly, lead with web results, and offer to `save_note` who they are after the meeting | | "Prep my day" | One compact card per meeting, ordered by time, sharpest points only |
Read more
name: meeting-prep description: Prep me for a meeting or call — who I'm meeting, background, talking points. Use for "prep me for", "get me ready for", "what should I know before", "who am I meeting", "brief me on my call with".
How to prep
1. Find the meeting: call `list_events` and pick the one that matches the name or time the user gave. Note the title, time, attendees, and notes. 2. Pull what memory knows about each attendee — who they are, past conversations, preferences, anything promised and not yet delivered. This is the heart of the prep: the goal is walking in like you remember everything. 3. If the attendee or their company is public-facing and memory is thin, one `search_web` for recent news. Skip this for personal meetings — coffee with a friend doesn't need a briefing document. 4. Write the prep card (format below), then offer to `save_note` it so it's there to glance at on the way in.
The prep card
- **When** — one line: time, duration, where/how.
- **Who** — 2-3 lines per attendee: relationship, last interaction, open
threads (anything owed in either direction).
- **Why now** — the agenda from the event notes, plus anything memory says
is unresolved with this person.
- **Three talking points** — concrete, memory first, web second. "Ask how
the Berlin launch went" beats "discuss recent developments".
Keep it skimmable — it gets read in the elevator, not at a desk.
Edge cases
| Situation | Do | |---|---| | No matching event on the calendar | Say so, then prep from the name alone using memory and web | | Several events match | Prep the next upcoming one; list the others in one line | | Memory knows nothing about the attendee | Say that plainly, lead with web results, and offer to `save_note` who they are after the meeting | | "Prep my day" | One compact card per meeting, ordered by time, sharpest points only |
Your own AI assistant. On your laptop. In code you can read in an afternoon. Meet Waku — a local-first personal assistant that shows the four pillars behind every serious agent: Harness · Loop · Memory · Eval/LLM-Ops. No frameworks hiding the good parts.
Other skills on waku-agent.
- /excalidraw
Generate an Excalidraw whiteboard in Sean's hand-drawn video style (Excalifont, roughness 1, green signature, socials + watermark, source labels). Use whenever the user wants a whiteboard, diagram, teaching board, or "chart" for a video or the docs/whiteboards gallery — anything
Open skill - /new-tool
Add a new tool to Waku the right way — schema, safe execution, deterministic eval, honest output. Use when adding or modifying agent tools or when the user asks for a new capability.
Open skill - /pr-worktree
Create and tear down the throwaway git worktrees used to test community PRs for waku-agent, without leaking API keys or leaving branches behind. Use when setting up to test a PR, and ALWAYS after a PR is merged, closed, or parked.
Open skill - /review-pr
Walk Sean through an incoming waku-agent PR or issue and present it his way — four fixed sections: what this is, why it matters, how HE can test it with you as copilot, and are we ready to merge / reply / close and why. Use whenever Sean asks to look at, test, triage, or decide
Open skill - /ship
Commit and push the current work properly — lint, run the release gate, write a detailed commit message, push to GitHub. Use whenever work reaches a milestone or the user says ship it, commit, or push.
Open skill - /pokedex
Look up any Pokemon's types, base stats, and abilities from the public PokeAPI. Use whenever the user mentions a specific Pokemon by name or asks about its stats, types, or abilities.
Open skill