agentleFS
analystacademyanalystacademy/claude-skills/meeting-prep/SKILL.md

meeting-prep

Skill35 starsChanged 6 months agoMITView on GitHub

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 web context about attendees or their company.

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use email-digest, meeting-followup and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • QuixiAISkill

    email-digest

    Digest and ingest emails into memory, surfacing important threads and action items

    Also in 3 projects that use this

  • yakatotechSkill

    meeting-followup

    Create meeting minutes and follow-up email from meeting notes in one workflow. Execute all post-meeting tasks at once

    Also in 3 projects that use this

  • vivy-yiSkill

    social-listening

    Use when needing to understand audience needs, monitor brand mentions, track competitor activities, discover trends, or gather market intelligence from Xiaohongshu conversations

    Also in 3 projects that use this

  • MicrosoftSkill

    inbox-triage

    Use this skill whenever the user asks to clean up, triage, declutter, or archive low-value Outlook inbox mail - "clean up my inbox", "triage my mail", "declutter my inbox", "sort out newsletters", "archive old resolved threads", "/inbox-triage" - to group only newsletters, auto-notifications, past-event meeting logistics, resolved threads, and redundant duplicates into reviewable move-proposals presented for per-bucket approval before any message moves. Do not use for reading mail, drafting or sending replies, deleting mail, executing moves without explicit per-bucket approval, or acting on messages from the user's manager, direct reports, active threads, flagged mail, or labelled/HR/Legal/Finance/Security senders.

    Also in 8 projects that use this

  • refly-aiSkill

    zoom

    Integrate with Zoom for video meetings. Use when you need to: (1) schedule Zoom meetings, (2) create instant meetings, or (3) manage meeting details and invitations programmatically.

    Also in 3 projects that use this

  • vijpatel7Skill

    cold-outreach

    Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 16 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 16

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Google Calendar to identify the meeting:

    line 17
  2. Distinctive:

    If the user asked about a specific meeting by name, search for it.

    line 18
  3. Distinctive:

    If the user asked generically ("prep me", "what's next"), fetch events for today and find the next upcoming meeting from the current time.

    line 19
  4. Distinctive:

    If triggered proactively (Claude notices it's ~20 min before a meeting starts), surface that meeting.

    line 20
  5. Distinctive:

    Search Gmail for recent threads involving the meeting attendees.

    line 28
  6. Distinctive:

    Search by attendee email addresses and/or names.

    line 31
  7. Distinctive:

    If you find emails from within the last 2 weeks, focus there.

    line 33
  8. Distinctive:

    If the last relevant email is older, expand to 1 month, then 3 months, stopping when you find substantive threads.

    line 34
  9. Distinctive:

    Check the calendar event's description field for:

    line 47
  10. Distinctive:

    If there's no agenda, note it so the user is aware.

    line 53
  11. Distinctive:

    If the meeting involves external attendees (people outside the user's organization) or company names are mentioned in the invite/emails:

    line 59
  12. Distinctive:

    Search the web briefly for recent news about those companies or individuals.

    line 60
  13. Distinctive:

    Keep this section tight — 2–3 bullets max.

    line 62
  14. Distinctive:

    Use plain language. Avoid restating obvious things.

    line 115
  15. Distinctive:

    If something is missing (no agenda, no prior emails), say so clearly — don't pad.

    line 116
  16. Distinctive:

    If the meeting is with many attendees (5+), focus email search on the organizer and any VIPs, not every attendee.

    line 117

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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.
  3. Thread summaries — brief summary of the 2–3 most relevant recent threads.
  4. Tone / relationship context — is this a new relationship, ongoing project, escalation, etc.?

Step 3: Extract Agenda from Invite

Check the calendar event's description field for:

  • A formal agenda
  • Pre-read materials or links
  • Goals or expected outcomes
  • Any notes the user added

If there's no agenda, note it so the user is aware.


Step 4: Optional Web Context

If the meeting involves external attendees (people outside the user's organization) or company names are mentioned in the invite/emails:

  • Search the web briefly for recent news about those companies or individuals.
  • Prioritize: funding rounds, product launches, leadership changes, recent press.
  • Keep this section tight — 2–3 bullets max. Skip if nothing relevant surfaces.

Step 5: Deliver the Briefing

Format the output as a clean, scannable briefing. Use this structure:


📅 [Meeting Title]

When: [Day, Date • Start–End Time] Where: [Location / Video link] With: [Attendee names and roles if known]


🗒️ Agenda

[Bullet points from invite, or "No agenda provided — consider setting one."]


📬 Email Summary

[2–3 sentence summary of recent threads with these attendees]

Key threads:

  • [Thread title / topic] — [1-line summary]
  • ...

✅ Open Action Items

  • [Action item] — owed by [person] (from [email date])
  • ...

(If none found: "No outstanding action items found in recent emails.")


🌐 Context & News (only if external attendees)

  • [Company/person]: [1-line recent news item]
  • ...

💡 Suggested Talking Points

Based on the above, 2–3 suggested things to raise or be ready to address.


Tone & Length

  • Be concise. The goal is a 60-second scan, not a report.
  • Use plain language. Avoid restating obvious things.
  • If something is missing (no agenda, no prior emails), say so clearly — don't pad.
  • If the meeting is with many attendees (5+), focus email search on the organizer and any VIPs, not every attendee.

Edge Cases

  • Internal all-hands or recurring standups: Skip email search unless the user asks. Just show agenda + time.
  • No attendees listed: Work with whatever info the invite has. Note the gap.
  • Multiple meetings in the next 30 min: Surface all of them, ask which one to prep for.
  • User asks for a specific meeting that's days away: Still run the full workflow, just note it's not imminent.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.