agentsclimarketplace

Meeting prep

Skill holzerjm/AgentDay-Example/projects/chief-of-staff/chief-of-stuff/skills/meeting-prep

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:".From its SKILL.md

Install
npx -y skills add holzerjm/AgentDay-Example --skill meeting-prep

Assembled 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 file declares

Copied from the file, not written here

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

  1. Anchor: meeting title, date, time, attendees — from the calendar entry.
  2. Mine the latest related note: where things stand, what was promised, what is still open.
  3. Turn the open items into numbered questions, most consequential first.
  4. 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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.