Source profileQuality 68/100Review permissions

sonichi/sutando/skills/meeting-prep/SKILL.md

meeting-prep

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

Source repository stars
359
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/sonichi/sutando --skill "skills/meeting-prep"
    Safe inspection promptEditorial

    Inspect the Agent Skill "meeting-prep" from https://github.com/sonichi/sutando/blob/6a8f0fccd32e5aa620a3572c8885544f144bb6fe/skills/meeting-prep/SKILL.md at commit 6a8f0fccd32e5aa620a3572c8885544f144bb6fe. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      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.

      Find the meeting. If ARGUMENTS specifies a meeting name or time, find it. Otherwise, find the next meeting starting within 60 minutes.Extract attendees. From the calendar event, get the list of attendee emails.Look up each attendee. For each attendee (skip the owner):
    2. 02

      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:

      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:
    3. 03

      Tips

      Skip recurring 1:1s unless the attendee is new or there are recent email threads

      Skip recurring 1:1s unless the attendee is new or there are recent email threadsFor large meetings (5 attendees), focus on the organizer and key participantsIf the meeting has an agenda doc linked, read and summarize it

    Permission review

    Static risk signals and limitations

    Runs scripts

    medium · line 24

    The documentation asks the agent to run terminal commands or scripts.

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

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score68/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars359SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    sonichi/sutando
    Skill path
    skills/meeting-prep/SKILL.md
    Commit
    6a8f0fccd32e5aa620a3572c8885544f144bb6fe
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original 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