meeting-prep-live
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.
npx skills add mohitagw15856/pm-claude-skills --skill meeting-prep-live --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## 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 1. **Why are we meeting** — the objective in one line; if it can't be stated, the meeting is the problem. 2. **Who's here and why** — each attendee's stake and likely
- What This Skill Produces
- Required Inputs
- Framework: What a Brief Must Answer
- Execution (Cowork)
- Output Format
- [Meeting title] · [time] · [chair/present/attend]
- Attendees
- Context (from the real thread & docs)
- Open threads / blockers
- Questions to ask
- Pre-read
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the meeting-prep-live skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill meeting-prep-live --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.