A Claude Code skill for the full meeting lifecycle: a private prep brief before the call, a shareable agenda going in, and a recap coming out. The three modes share one memory loop, so each meeting builds on the last. Prep reads the previous recap. The recap threads under the agenda. Open action items carry forward until someone closes them. It is built for people running recurring internal syncs and external client calls, where the value is not any single artifact but the thread that connects them week over week.
:memo: **Northwind pilot launch sync recap - Aug 5**
> 🟡 **Aug 10 launch holds for Riverton and Bend. Kelso slips to Aug 14 on the parts delay.**
:white_check_mark: **Decisions**
• **Split the ship date:** Riverton and Bend go Aug 10, Kelso follows Aug 14 [Sofia]
• **One go/no-go call:** single pilot call Aug 9, 10-10:30am, Priya chairs [Dan]
• **Kelso is not a blocker:** launch proceeds even if Kelso parts are still in transit [Sofia]
:arrows_counterclockwise: **In motion**
• **Kelso parts:** carrier ETA Aug 8, Ren tracking daily
• **Operator training:** Riverton set, Bend and Kelso still being scheduled with Marcus
• **Security sign-off:** data migration review due back Aug 6
:pushpin: **Sofia**
• Send the split-date plan to Priya and Marcus by end of day Aug 5
• Confirm the Bend install crew for the Aug 10 window
:pushpin: **Dan**
• Get the Aug 9 go/no-go on Priya's calendar
• Chase Bend and Kelso training slots with Marcus by Aug 7
:pushpin: **Ren**
• Confirm Kelso parts have landed before the Aug 9 callExternal recaps use an email format instead, warmer and prose-first. See examples/ for the full set: prep brief, internal agenda, internal recap, and client recap email.
git clone https://github.com/milock/meetings.git
cd meetings
./install.shThat copies SKILL.md and references/ into ~/.claude/skills/meetings. Pass a path to install somewhere else: ./install.sh /some/other/dir.
To install by hand instead, copy SKILL.md and the references/ folder into ~/.claude/skills/meetings/ yourself. That is all the skill needs to run.
| Mode | Produces | Goes to |
|---|---|---|
/meetings prep |
Private brief before the call | Saved only, never delivered |
/meetings agenda |
Shareable agenda | Chat message or email draft |
/meetings recap |
Decisions, status, action items | Chat thread or email draft |
The skill reads and delivers through whatever connectors your session already has. It describes them by capability, not by product, so any tool that provides the capability qualifies. Nothing here is required. Miss all of them and every mode still produces its file and puts it on your clipboard.
| Capability | Used for | Without it |
|---|---|---|
| Calendar | Resolve the meeting, pull time, attendees, and links | You name the meeting; the skill asks for what it needs |
| Read recent threads with attendees; deliver external agendas and recaps as drafts | External output lands as a file plus clipboard for you to paste | |
| Meeting notes | Fetch the transcript or AI notes to build the recap | You paste the notes; recap works the same |
| Chat | Search channel history; post the agenda and thread the recap under it | Internal output lands as a file plus clipboard |
| GitHub context repo | Pull standing notes for a client or series from a repo you point to | The skill runs on session context and series history alone |
No hard dependencies. Everything degrades to file plus clipboard.
State lives as plain markdown under meetings/ in your working directory, one folder per recurring series or client:
meetings/
config.md # optional defaults: name, sign-off, per-series audience
northwind-launch/
2026-08-05-agenda.md
2026-08-05-recap.md
2026-08-12-prep.md
The chain works like this:
- Prep reads the newest recap in the series folder and surfaces its unresolved action items, so you walk in knowing what is still open.
- Agenda posts as a top-level chat message and records the message timestamp in its front-matter.
- Recap threads as a reply under that day's agenda, so the agenda and the outcome stay together in one place.
- Open items carry forward on their own. The recap resolves or re-carries each one explicitly. Nothing drops silently, and an item carried a third time gets flagged.
meetings/config.md is optional. Drop in a name, a default sign-off, and per-series audience defaults, and the skill stops asking. Anything you say in the moment overrides it.
Run a voice-scrubbing skill such as humanizer as the last pass before you send. This skill handles the structure and the memory; a scrubbing pass catches the tells that make a draft read like a machine wrote it.
MIT. See LICENSE.