Meeting Prep (Live)
Walking into a meeting cold costs the first ten minutes. In Claude Cowork this skill assembles the brief from the user's real calendar and files — the event, who's in the room, what's attached, and where the last conversation left off — so they arrive with the context already in hand.
Not quite this? Use meeting-prep-pack when you will paste the agenda and documents yourself instead of connecting a calendar; use sop-meeting-prep when you mean S&OP, the supply-chain sales and operations planning meeting.
What This Skill Produces
- The meeting-brief artifact — objective, attendees with why-they-matter, the relevant context pulled from real docs/threads, open decisions, and a short list of questions to drive
- A pre-read pack — links to the actual Drive docs and the last thread, so nothing needs re-finding mid-meeting
- The one thing to decide — the single outcome that makes the meeting worth holding
Required Inputs
Ask for these if not provided:
- Which meeting — the next one, a named event, or a time ("my 2pm")
- The user's role in it — chairing, presenting, or attending — the brief's angle follows
- Depth — a 30-second glance or a full pre-read
Framework: What a Brief Must Answer
- Why are we meeting — the objective in one line; if it can't be stated, the meeting is the problem.
- Who's here and why — each attendee's stake and likely position.
- Where we left off — the last decision/blocker from the real thread, not memory.
- What must be decided — the outcome; everything else is discussion.
- What the user should ask — 3–5 questions that move it forward.
Execution (Cowork)
- Find the event — via the Google Calendar connector, resolve the meeting (next, named, or by time). Read title, description, attendees, and any attached links.
- Gather context — open the attached Drive docs; via Gmail/Slack connectors, pull the most recent thread with those attendees on this topic. Read, don't guess.
- Synthesise — fill the five questions above from what was actually found; mark anything you couldn't find as a gap rather than inventing it.
- Emit the artifact — the one-page brief with live links to the sources.
- Offer the next action — e.g. "draft an agenda from this?" — but don't take it unasked.
Guardrails: cite the real source for every claim; never fabricate an attendee position or a decision that isn't in the material; if a connector is unauthorised, produce the brief from what's available and name the gap.
Output Format
A Meeting Brief artifact:
[Meeting title] · [time] · [chair/present/attend]
Objective: one line · Decision needed: the one outcome
Attendees
| Person |
Stake / likely position |
Context (from the real thread & docs)
- key point — source: [doc/thread link]
Open threads / blockers
Questions to ask
- …
Pre-read
Quality Checks
Anti-Patterns
- Inventing attendee views to fill the table — mark unknowns.
- A brief with no decision — then question whether the meeting should happen.
- Summarising a doc you didn't open — read the real file or flag it missing.
- Auto-creating an agenda or sending anything without being asked.
Example Trigger Phrases
- "Prep me for my next meeting in Cowork."
- "Get me ready for the 2pm with the design team."
- "What do I need for the sync with Acme tomorrow?"
- "Pull the context for my 1:1 and give me questions to ask."
1---2name: meeting-prep-live3description: "Prepare the user for a REAL upcoming meeting by pulling the actual Calendar event, its attendees, the linked Drive docs, and the last email/Slack thread — then producing a brief. Use when asked to prep me for my next meeting, get me ready for the 2pm, or what do I need for the sync with X in Cowork. Reads the event via the Google Calendar connector, gathers the attached and related material via Drive/Gmail, and produces a one-page meeting-brief artifact with objective, context, open threads, and the questions to ask."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/meeting-prep-live7---89# Meeting Prep (Live)1011Walking into a meeting cold costs the first ten minutes. In Claude Cowork this skill assembles the brief from the user's *real* calendar and files — the event, who's in the room, what's attached, and where the last conversation left off — so they arrive with the context already in hand.1213> **Not quite this?** Use `meeting-prep-pack` when you will paste the agenda and documents yourself instead of connecting a calendar; use `sop-meeting-prep` when you mean S&OP, the supply-chain sales and operations planning meeting.1415## What This Skill Produces1617- **The meeting-brief artifact** — objective, attendees with why-they-matter, the relevant context pulled from real docs/threads, open decisions, and a short list of questions to drive18- **A pre-read pack** — links to the actual Drive docs and the last thread, so nothing needs re-finding mid-meeting19- **The one thing to decide** — the single outcome that makes the meeting worth holding2021## Required Inputs2223Ask for these if not provided:24- **Which meeting** — the next one, a named event, or a time ("my 2pm")25- **The user's role in it** — chairing, presenting, or attending — the brief's angle follows26- **Depth** — a 30-second glance or a full pre-read2728## Framework: What a Brief Must Answer29301. **Why are we meeting** — the objective in one line; if it can't be stated, the meeting is the problem.312. **Who's here and why** — each attendee's stake and likely position.323. **Where we left off** — the last decision/blocker from the real thread, not memory.334. **What must be decided** — the outcome; everything else is discussion.345. **What the user should ask** — 3–5 questions that move it forward.3536## Execution (Cowork)37381. **Find the event** — via the Google Calendar connector, resolve the meeting (next, named, or by time). Read title, description, attendees, and any attached links.392. **Gather context** — open the attached Drive docs; via Gmail/Slack connectors, pull the most recent thread with those attendees on this topic. Read, don't guess.403. **Synthesise** — fill the five questions above from what was actually found; mark anything you *couldn't* find as a gap rather than inventing it.414. **Emit the artifact** — the one-page brief with live links to the sources.425. **Offer the next action** — e.g. "draft an agenda from this?" — but don't take it unasked.4344Guardrails: cite the real source for every claim; never fabricate an attendee position or a decision that isn't in the material; if a connector is unauthorised, produce the brief from what's available and name the gap.4546## Output Format4748A **Meeting Brief** artifact:4950### [Meeting title] · [time] · [chair/present/attend]51**Objective:** one line · **Decision needed:** the one outcome5253### Attendees54| Person | Stake / likely position |55|---|---|5657### Context (from the real thread & docs)58- key point — *source: [doc/thread link]*5960### Open threads / blockers61- …6263### Questions to ask641. …6566### Pre-read67- [doc/thread links]6869## Quality Checks70- [ ] Every context point cites a real Calendar/Drive/Gmail/Slack source71- [ ] Attendee positions are drawn from material, not invented72- [ ] The single decision-needed is stated73- [ ] Gaps (couldn't find X) are named, not papered over74- [ ] Links resolve to the actual documents7576## Anti-Patterns77- **Inventing attendee views** to fill the table — mark unknowns.78- **A brief with no decision** — then question whether the meeting should happen.79- **Summarising a doc you didn't open** — read the real file or flag it missing.80- **Auto-creating an agenda or sending anything** without being asked.8182## Example Trigger Phrases83- "Prep me for my next meeting in Cowork."84- "Get me ready for the 2pm with the design team."85- "What do I need for the sync with Acme tomorrow?"86- "Pull the context for my 1:1 and give me questions to ask."