borghei/Claude-Skills / personal-productivity/calendar-prep
calendar-prep
VerifiedGenerate one-page meeting briefings from structured input (attendees, prior context, decisions needed). Use before customer calls, board meetings, or 1:1s to prepare a pre-read or briefing.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.9 KB |
| assets/meeting_input.json | config | 3.0 KB |
| references/briefing_methodology.md | markdown | 3.0 KB |
| scripts/meeting_prep_briefer.py | script | 5.2 KB |
references/briefing_methodology.md
View on GitHub# Briefing Methodology
Every meeting deserves a 30-second-or-less mental rehearsal of: **what's the goal, who am I trying to convince of what, and what's my fallback.** A written briefing is that rehearsal made permanent.
---
## When Briefings Help
- **High-stakes meetings** — board, investors, customer renewals, M&A
- **Multi-stakeholder meetings** — when you need to manage three or four agendas in one room
- **Returning meetings** — second / third meetings on the same topic where context drift is likely
- **Pre-meetings before bigger meetings** — alignment-building rounds with key stakeholders
## When Briefings Are Overhead
- **Standups** — too short, too frequent
- **Spontaneous pair work** — destroys the spontaneity
- **Recurring 1:1s with someone you talk to every day** — already aligned
The line: if you'd benefit from re-reading prior context, you'd benefit from a briefing.
---
## What Goes In a Briefing
**The decision** — what specifically are you trying to decide? "Discuss the roadmap" is not a decision; "approve Q3 priorities" is.
**The attendees and their positions** — who's likely to be for, against, neutral. What's their motivation?
**Talking points** — your strongest 3-5 points, ordered by importance.
**Counter-arguments to anticipate** — what objections do you expect, and what's your response?
**Questions to ask** — the things you don't know that you need to find out.
**Metrics** — the numbers that anchor the discussion.
**Success and fallback** — best case + acceptable case + walk-away.
---
## What Doesn't Go In a Briefing
- Long history. Use links, not paragraphs.
- Your full deck. The deck is for the meeting; the briefing is for you.
- Speculation about other attendees' motivations expressed disrespectfully (that briefing will leak).
- Personal commentary on attendees that you wouldn't want repeated.
---
## Length Discipline
- **Target:** 1 page (300-400 words)
- **Maximum:** 1.5 pages
- Beyond that: you'll skim it; the briefing fails its job.
---
## Reading the Briefing
Generate the briefing the day before. Read it 30-60 minutes before the meeting. Re-read the **decisions and fallback** in the 5 minutes before walking in.
If you generate a briefing and don't read it, you've performed the ritual without getting the value.
---
## Common Pitfalls
- **Padding.** Adding sections to feel thorough — brief is the point.
- **No counter-arguments.** Briefings without anticipated counters are wishful thinking.
- **Same template everywhere.** A board briefing is not a 1:1 briefing.
- **Briefing for show.** Writing a briefing the team will see, not for yourself, distorts the writing.
- **No update for second meeting.** Re-using the prior briefing without updating context misleads.
---
## After the Meeting
The briefing's questions should be answered in the meeting's decisions. Pair with `personal-productivity/meeting-insights/` to extract decisions, action items, owners, and dates from the meeting transcript.
If the meeting closed your briefing's open questions, the briefing did its job.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |