/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.
$ npx -y skills add sonichi/sutando --skill meeting-prep --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/meeting-prep
Context preview
The summary Claude sees to decide when to auto-load this skill.
Auto-prepare for upcoming meetings: attendee info, recent email threads, talking points, and agenda. Runs 30 min before each meeting or on demand.
SKILL.md
meeting-prep.SKILL.mdname: meeting-prep
description: "Auto-prepare for upcoming meetings: attendee info, recent email threads, talking points, and agenda. Runs 30 min before each meeting or on demand."
user-invocable: true
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
2. **Extract attendees.** From the calendar event, get the list of attendee emails.
3. **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.
4. **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]
5. **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
Read more
name: meeting-prep description: "Auto-prepare for upcoming meetings: attendee info, recent email threads, talking points, and agenda. Runs 30 min before each meeting or on demand." user-invocable: true
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
2. **Extract attendees.** From the calendar event, get the list of attendee emails.
3. **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.
4. **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]
5. **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
My AI Stand — Realtime by Day, Rewriting Itself by Night. Summon my AI superpower. Voice, vision, screen, meetings, calls when I'm engaged. Learns my patterns, ships its own code when I'm not. Runs across my Macs, interacts with people & their Stands.
Repo: sonichi/sutando
Other skills on sutando.
- /agent-registry
Local Agent Registry — a standalone, dependency-free service that tracks running Claude Code (and other) agent instances. Agents self-register on startup and heartbeat while alive; the Electron overlay and Sutando dashboard read the live list. Use when you need to know which
Open skill - /agent-room-ops
**One skill, multiple tools.** Everything an agent does in a room beyond its task inbox lives here as a tool, so the parity capabilities are self-evidently *one collection* (not N scattered skills). Each tool is a thin **gateway-only** client verb sharing `_gateway.py`; the
Open skill - /audio-transcribe
Transcribes audio files and voice notes to text via Gemini 2.5-flash. Integrates with Slack, Discord, and Telegram bridges so voice clips surface as readable text in tasks.
Open skill - /bot2bot-post
Post a coordination message from this bot to the shared bot2bot channel — @-mentioning a specific peer via --to, auto-mentioning only in single-peer fleets, never guessing.
Open skill - /call-diagnostics
Analyze phone call observability data, detect problems, track them across calls, and recommend systematic repairs.
Open skill - /claude-codex
Bash wrapper around the local Codex CLI for non-interactive runs from inside Sutando (bridges, cron, scripts). For interactive code review or task hand-off from this Claude Code session, prefer the official `/codex:*` plugin commands; this skill is the file-bridge-compatible
Open skill

