agentleFS
Sign inStart free
sonichisonichi/sutando/skills/meeting-prep/SKILL.md

meeting-prep

Skill396 starsChanged 6 months agoMITView on GitHub

Auto-prepare for upcoming meetings: attendee info, recent email threads, talking points, and agenda. Runs 30 min before each meeting or on demand.

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 9 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

  • 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

  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 10 projects that use this

  • +1 more from QuixiAI

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Find the meeting: If ARGUMENTS specifies a meeting name or time, find it.

    line 17
  2. Distinctive:

    Read the top 2-3 threads to extract context.

    line 37
  3. Very specific:

    Deliver: Write to results/meeting-prep-{timestamp}.txt so the voice agent can speak it.

    line 64
  4. Distinctive:

    If the meeting has an agenda doc linked, read and summarize it

    line 79
  5. Distinctive:

    Keep the brief voice-friendly — it will be spoken aloud

    line 80

“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

Prepare a briefing for an upcoming meeting — attendee info, recent context, and talking points.

Usage: /meeting-prep [meeting name or time]

ARGUMENTS: $ARGUMENTS

How it works

  1. Find the meeting. If ARGUMENTS specifies a meeting name or time, find it. Otherwise, find the next meeting starting within 60 minutes.
$CLAUDE_CONFIG_DIR/skills/google-calendar/scripts/google-calendar.py events list \
  --time-min NOW --time-max NOW_PLUS_60MIN
  1. Extract attendees. From the calendar event, get the list of attendee emails.

  2. Look up each attendee. For each attendee (skip the owner):

    a. Contacts — search by email:

    python3 $CLAUDE_CONFIG_DIR/skills/macos-tools/scripts/contacts.py search "email@example.com"

    b. Recent emails — search Gmail for recent threads with this person:

    gws gmail users messages list --params 'q=from:email@example.com OR to:email@example.com newer_than:14d'

    Read the top 2-3 threads to extract context.

    c. Web presence — if the person is external or unfamiliar, do a quick web search for their name + company to understand their role.

  3. Build the brief. Generate a concise prep document:
Meeting: [title]
Time: [start] - [end]
Location: [link or room]

Attendees:
- [Name] ([role/company]) — [1-line context from recent emails]
- ...

Recent context:
- [Key thread 1 summary]
- [Key thread 2 summary]

Suggested talking points:
- [Based on recent threads and meeting title]
- ...

Action items to follow up on:
- [Any commitments from prior meetings/emails]
  1. Deliver. Write to results/meeting-prep-{timestamp}.txt so the voice agent can speak it. Also write to notes/meeting-prep-{date}-{title-slug}.md for reference.

Auto-scheduling

The proactive loop should check for meetings starting in the next 30-45 minutes. If one is found and no prep exists yet, run this skill automatically. Add this check to the proactive loop:

Check calendar for meetings in next 30-45 min.
If found and no notes/meeting-prep-{date}-{slug}.md exists, run /meeting-prep.

Tips

  • Skip recurring 1:1s unless the attendee is new or there are recent email threads
  • For large meetings (>5 attendees), focus on the organizer and key participants
  • If the meeting has an agenda doc linked, read and summarize it
  • Keep the brief voice-friendly — it will be spoken aloud

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.

Check your setup, free