mcpbeat

Calendar Prep

borghei/calendar-prep

> Generate one-page meeting briefings from structured input (attendees, prior context, decisions needed). Use before customer calls, board meetings, or

4k tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
447
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/borghei/Claude-Skills --skill calendar-prep

What comes with it

11 434 bytes besides the instruction
assets/meeting_input.json
references/briefing_methodology.md
scripts/meeting_prep_briefer.py

The instruction itself

13 sections, as written by the author

Calendar Prep

Convert structured meeting context into a one-page briefing in seconds.


Keywords

meeting prep, calendar prep, briefing, pre-read, pre-meeting, talking points, agenda, board meeting, customer call, 1:1


Clarify First

Before generating the briefing, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Meeting type & attendees — customer call vs board vs 1:1 changes the briefing's structure, tone, and emphasis
  • [ ] Your goal / decision sought — this becomes the front-loaded first line of the briefing
  • [ ] Prior context — last contact, open issues, current status; without it the briefing is generic and useless

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


Quick Start

  • Fill in assets/meeting_input.json with attendees, context, decisions needed, supporting links
  • Run: python scripts/meeting_prep_briefer.py meeting_input.json
  • Read the briefing 5 minutes before the meeting

Core Workflows

Workflow 1: Customer Call Prep

  • Pull the customer's recent activity, last meeting notes, current account status
  • Fill input JSON with: attendees, last contact, open issues, your goal, decisions you're trying to make
  • Run briefer
  • Walk in knowing: what you want, what they want, where you have leverage

Time Estimate: 10-15 minutes per major customer call.

Workflow 2: Board / Investor Meeting Prep

  • Pull metrics dashboard, prior board deck, last investor update
  • Build input JSON; emphasize decisions sought from the board
  • Pair output with documents/pptx-toolkit/ deck audit

Time Estimate: 30-60 minutes per board meeting.

Workflow 3: Manager 1:1 Prep

  • Compress the past two weeks: top 3 wins, top 3 challenges, top 3 asks
  • Run briefer
  • Lead with asks (1:1s default to status; the leverage is in asking)

Time Estimate: 5-10 minutes per 1:1.


Tools

meeting_prep_briefer.py

Reads a structured JSON input describing meeting context and produces a one-page briefing in markdown.

python scripts/meeting_prep_briefer.py meeting_input.json
python scripts/meeting_prep_briefer.py meeting_input.json --json

Reference Guides

  • references/briefing_methodology.md — When briefings help and when they don't, format conventions

Templates

  • assets/meeting_input.json — Input file template

Best Practices

  • One page max. A 3-page briefing is one you won't read.
  • Front-load the decision. The first sentence should be the decision you want.
  • Read the briefing. Generating one without reading it is performance theater.
  • Capture outputs. Pair with personal-productivity/meeting-insights/ post-meeting to convert the briefing's questions into the meeting's decisions.

How to use it

Copy the folder

Take borghei/calendar-prep from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.