Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/meeting-closeout
Close out the meeting you just had while it's fresh — lock the decisions, the action items and who owns each, what you personally committed to, and the single next step — then capture it and, only with your OK, turn the actions into tracked tasks.
Passed 12 of 17 test cases with the skill, and 9 of 17 without it.
and 5 more in the full report
6 fixed9 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Here are notes pulled from an existing provider file located at `00-Inbox/Meetings/ClickUp_Sync_102.md`. After extracting decisions and action items, where should the completed closeout block be saved? I might usually assume all new closeouts go to `00-Inbox/Meetings/New_Closeout.md`.
| Checked | Without skill | With skill |
|---|---|---|
| Saves the closeout summary into 00-Inbox/Meetings/ClickUp_Sync_102.md. | Missed | Passed |
| Refrains from creating a new file in 00-Inbox/Meetings/. | Passed | Passed |
The instructions your model reads when the skill loads.
The gap between walking out of a meeting and the next context switch is where decisions and promises evaporate. This closes one meeting the moment it ends — while you still remember who said they'd do what — and locks it down.
It is the single-meeting, in-the-moment ritual. It is not the bulk "catch up all my synced notes" pass (process-meetings) and not pre-meeting prep (meeting-prep).
Work from whichever exists, in this order:
get_meeting_context.meeting_sources in
System/user-profile.yaml. If a notes_folder is set, search that folder for
the meeting by title, attendee, and date before anything else. A configured
source always outranks improvised discovery.00-Inbox/Meetings/. Exclude Dex internals, dependency folders, archives that
fall outside the requested date, and binary files. Prefer QMD when available,
otherwise use a bounded Markdown filename/content search. Read the matched note
before treating it as the meeting.Source boundary (hard rule). Meeting notes come from the vault (and the
configured meeting_sources folder) only. Never go looking in external services —
Google Drive, Gemini notes, Notion, email, or any connected tool — for a meeting
the vault doesn't have, unless the user explicitly points at that source for this
meeting in this conversation. Auto-generated notes from an unconfigured source can
describe a different meeting or contain invented content, and a closeout built on
them is worse than no closeout.
If there are no notes and no matching vault note, the search is over — ask for the notes (or a two-line recap) — do not fabricate a summary of a meeting you can't see, and do not widen the search to external tools.
test cases passed, vs 9 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.