Meeting prep
Skill holzerjm/AgentDay-Example/projects/chief-of-staff/chief-of-stuff/skills/meeting-prep
Starter agents + skills for TOA Agent Build Day (June 27, 2026) — 9 fork-ready projects, agentskills.io-spec skills, measured evals, local-first
npx -y skills add holzerjm/AgentDay-Example --skill meeting-prepAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Produces a one-page prep sheet for a single upcoming meeting from briefcase sources (the calendar entry, the most recent related notes, related todos). Use whenever asked to prep for a meeting, "get me ready for X", build a meeting one-pager, or when a task starts with "prep:".
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.2 KB, 425 tokens by cl100k_base, as published. Nobody here has run it
Meeting Prep One-Pager
Get one person ready for ONE meeting in two minutes of reading. The inputs are this meeting's calendar entry, the latest related notes, and any related todos. Everything else in the working life is somebody else's problem for the next hour.
Defaults (do not present options)
- Pull ONLY from the briefcase sources provided. No outside knowledge.
- Unanswered questions from the last notes lead — they ARE the agenda.
- One page max. If it doesn't move THIS meeting, it doesn't go in.
Workflow
- Anchor: meeting title, date, time, attendees — from the calendar entry.
- Mine the latest related note: where things stand, what was promised, what is still open.
- Turn the open items into numbered questions, most consequential first.
- Name the single outcome to drive, then at most two ways it goes sideways.
Gotchas
- Don't summarize the whole relationship history — only what moves THIS meeting. Prep sheets die of completeness.
- No attendee psychoanalysis ("Priya seems defensive"). Facts and asks only.
- If the meeting is not on the calendar, say exactly that in ## Meeting and prep from the notes anyway — never invent a time.
- A promised deliverable with a deadline ("before Friday's sync") goes in
Your ask or ## Landmines, never buried mid-paragraph.
Output template
Produce EXACTLY these five sections, in this order, with these headings:
Meeting
Title — date, HH:MM, attendees (from the calendar entry only).
Where it left off
2–4 lines: the state of play after the last touchpoint, citing the note file in parentheses.
Open questions
Numbered 1.–N: the unanswered questions, most consequential first.
Your ask
One sentence: the single outcome to drive in this meeting.
Landmines
At most 2 bullets: ways this meeting goes sideways, each grounded in a source fact.
Gives 0 of the 12 instructions most note taking skills give in 425 tokens
Counted across 686 of the 876 authors here whose files we hold, read 2026-08-07
- include a visual element on every slidein 44 of 686, across 13 files
- use wikilinks for internal vault linksin 36 of 686, across 12 files
- commit to a single visual motif across every slidein 34 of 686, across 9 files
- use subagents to visually inspect rendered slidesin 31 of 686, across 7 files
- read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
- keep 0.5 inch minimum marginsin 30 of 686, across 7 files
- re-verify affected slides after every fixin 27 of 686, across 5 files
- run content QA checks before declaring successin 26 of 686, across 3 files
- Use Markdown links for external URLs onlyin 26 of 686, across 11 files
- pick a bold topic specific color palettein 24 of 686, across 2 files
- read editing guide before editing existing presentationsin 23 of 686, across 1 file
- use one dominant color across all slidesin 23 of 686, across 1 file
Said here and by no other author read
- Pull only from the provided briefcase sources
- Lead with unanswered questions from the latest notes
- Keep the prep sheet to one page maximum
- Extract the state of play from the latest related note
- Order open questions by consequence
- Name a single outcome to drive
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.