Meeting Prep

Prepare a comprehensive pre-meeting briefing by pulling together everything you need to walk in ready. Use this skill whenever the user asks to "prep me for my meeting", "what do I have coming up", "brief me before my call", "meeting prep", "get me ready for [meeting name]", or any similar phrasing. Also trigger automatically when the user opens Claude and there is a meeting starting within the next 20–30 minutes — proactively offer the briefing without waiting to be asked. Covers upcoming calendar events, attendee email history, open action items, agenda/notes from the invite, and optional we

43 stars 14 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add analystacademy/claude-skills --skill meeting-prep
Manual install
git clone --depth 1 https://github.com/analystacademy/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/meeting-prep ~/.claude/skills/meeting-prep

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Meeting Prep Skill

Generate a concise, actionable pre-meeting briefing by combining calendar data, email history, and optional web research.

---

## Workflow

### Step 1: Find the Target Meeting

Use Google Calendar to identify the meeting:
- If the user asked about a **specific meeting by name**, search for it.
- If the user asked generically ("prep me", "what's next"), fetch events for today and find the **next upcoming meeting** from the current time.
- If triggered proactively (Claude notices it's ~20 min before a meeting starts), surface that meeting.

Fetch the full event details: title, start/end time, location or video link (Zoom/Meet/Teams URL), description/agenda, and **attendee list with email addresses**.

---

### Step 2: Pull Email Context

Search Gmail for recent threads involving the meeting attendees.

**Search strategy:**
- Search by attendee email addresses and/or names.
- Determine how far back to look *smartly*:
  - If you find emails from within the last **2 weeks**, focus there.
  - If the last relevant email is older, expand to **1 month**, then **3 months**, stopping when you find substantive threads.
  - For brand-new contacts (no prior email history), note this explicitly.

**What to extract from emails:**
1. **Open action items** — anything that was promised, assigned, or requested but doesn't appear to have been resolved. Flag who owes what.
2. **Key discussion points** — topics that came up in recent threads relevant to this meeting.
Read the full skill on GitHub

Details

Skill name
meeting-prep
Path
meeting-prep/SKILL.md
License
MIT
Repo updated
6 May 2026

FAQ

What does the Meeting Prep skill do?

Prepare a comprehensive pre-meeting briefing by pulling together everything you need to walk in ready. Use this skill whenever the user asks to "prep me for my meeting", "what do I have coming up", "brief me before my call", "meeting prep", "get me ready for [meeting name]", or any similar phrasing. Also trigger automatically when the user opens Claude and there is a meeting starting within the next 20–30 minutes — proactively offer the briefing without waiting to be asked. Covers upcoming calendar events, attendee email history, open action items, agenda/notes from the invite, and optional we

How do I install the Meeting Prep skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add analystacademy/claude-skills --skill meeting-prep. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Meeting Prep popular?

It lives in analystacademy/claude-skills, which has 43 GitHub stars and 14 forks.

Related skills

Ask Hr

43

analystacademy/claude-skills

Review any piece of content through a strict corporate HR lens, flagging offensive language, cultural insensitivity, stereotypes, exclusionary framing, cancel-risk phrasing, and other blindspots. Use this skill whenever the user asks to "HR check", "screen", "review for sensitivity", "check before I post", "is this okay to say", or pastes content and wants to know if it's safe. Also trigger when the user submits emails, social posts, blog drafts, scripts, or any written content and asks for feedback, a review, or a safety check — even if they don't use the words "HR" or "offensive". Err on the

Marketing, Sales & Business14

Brainstorm

43

analystacademy/claude-skills

Help the user brainstorm a topic in a structured, conversational way — like a really smart, honest friend. Use this skill whenever the user wants to think something through, explore an idea, work through a decision, or just talk something out. Trigger on phrases like "help me brainstorm", "I want to think through", "let's explore", "I'm trying to figure out", "help me think about", "I have an idea I want to explore", "can we brainstorm", or any time the user brings up a topic they seem to want to reason through together rather than just get a quick answer on. Prefer this skill even if the requ

Other14

Content

43

analystacademy/claude-skills

Turn any content into 3-4 finished LinkedIn posts ready to publish. Use this skill whenever the user shares something and wants LinkedIn posts from it — a PDF, an email, a newsletter, a URL, pasted text, a report, or anything else. Trigger on phrases like "turn this into posts", "what can I post about this", "LinkedIn content from this", "post ideas", "what should I post", or any time the user shares a piece of content and seems to want to repurpose it for LinkedIn.

Writing & Content14

Release Notes

49

petekp/claude-code-setup

Write release notes or a changelog entry that tell existing users what they will notice after updating, with the technical detail after it. Use when publishing a release, writing a changelog, or editing release notes.

Productivity & Notes10

Find Skill

43

analystacademy/claude-skills

Search curated, trusted sources for installable agent skills that match what the user is trying to do, and return a short list of candidates with a one-line summary and link to each. Use this skill whenever the user asks to find, discover, look for, browse, or install skills — including phrasings like "is there a skill for X", "find me a skill that does Y", "what skills exist for Z", "I need a skill to handle W", or any time the user describes a repetitive task and wonders aloud whether a packaged skill exists. Also use when the user mentions a tool/workflow gap and is open to extending Claude

Productivity & Notes14

Vignette Todo Run

49

petekp/claude-code-setup

Run a batch of Vignette TODO items as a multi-agent worktree run. Use when Pete asks to "run the TODOs", "run items N to M", "do a todo run", or hands over queued items from docs/TODOS.md in the Vignette repo. The orchestrator plans, briefs, and reviews; delegated coding agents do every code change and every verification, each in its own worktree with its own scratch settings; an integrator merges, a reviewer attacks the merge, and the branch is handed to Pete unmerged. Not for a single small fix in the checkout, and not for a repo other than Vignette.

Productivity & Notes10

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.