القائمة
Auto-prepare for upcoming meetings: attendee info, recent email threads, talking points, and agenda. Runs 30 min before each meeting or on demand.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Make conversational phone calls and join Zoom meetings via Twilio + Gemini. Multi-turn AI conversations on the phone on behalf of the user.
File a bug report, feature request, or feedback about Sutando to the team from any surface (chat, Discord, Telegram, or a voice-delegated task). Reuses the cloud /api/feedback API and auto-attaches diagnostic context. Use when the user says "report a bug", "something's broken, file it", "I have a feature request", etc.
Track Claude Code quota usage via Anthropic API rate limit headers. Shows 5h and 7d utilization, reset times, and quota status. Works with both subscription and API key auth.
Zoom meeting control for Sutando's voice and phone agents — contributes the summon (join + screen share), dismiss (leave meeting), and join_zoom (join with computer audio, no share) inline tools.
Framework + minimal example for Sutando desktop overlay applications — always-on-top, frameless Electron windows that float over the desktop, controllable from the Sutando web UI's /overlays manager. Ships one example overlay (System Resources). Add new overlays by registering them in app/main.js.
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 coding agents are running, where, and since when.
| 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 |
Prepare a briefing for an upcoming meeting — attendee info, recent context, and talking points.
Usage: /meeting-prep [meeting name or time]
ARGUMENTS: $ARGUMENTS
$CLAUDE_CONFIG_DIR/skills/google-calendar/scripts/google-calendar.py events list \
--time-min NOW --time-max NOW_PLUS_60MIN
Extract attendees. From the calendar event, get the list of attendee emails.
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.
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]
results/meeting-prep-{timestamp}.txt so the voice agent can speak it. Also write to notes/meeting-prep-{date}-{title-slug}.md for reference.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.