Menu
Post a coordination message from this bot to the shared bot2bot channel, @-mentioning the other Sutando node.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | bot2bot-post |
| description | Post a coordination message from this bot to the shared bot2bot channel, @-mentioning the other Sutando node. |
Post a coordination message from this Sutando node to the other in the shared #bot2bot Discord channel. The receiving bot's bridge processes @-mention messages from other bots as tasks (see src/discord-bridge.py:244), so prefixing with <@other-bot> routes the post to the other bot's loop.
python3 skills/bot2bot-post/post.py <kind> <text>
Kinds:
claim — "I'm taking this work, ETA X"blocked — "I'm stuck on X, need eyes"done — "shipped X, FYI"ping — "you there?"opinion — "what do you think about X?"Examples:
python3 skills/bot2bot-post/post.py claim "refactor task-bridge task-file schema ETA 20m"
python3 skills/bot2bot-post/post.py done "shipped PR #472 — kickstart web-client after merge"
python3 skills/bot2bot-post/post.py opinion "is Discord-as-state better than files for coord?"
$CLAUDE_CONFIG_DIR/channels/discord/access.json — pick the groups entry tagged {"role": "bot2bot", ...}, fallback to any entry with value true.DISCORD_BOT_TOKEN read from $CLAUDE_CONFIG_DIR/channels/discord/.env.allowFrom list, excluding this bot's own ID (fetched via Discord /users/@me).Before this skill: bot A could reply in a task-triggered channel (existing pending_replies path) and DM the owner (poll_proactive), but had no way to initiate a channel post. That made cross-bot coord invisible to Chi and impossible without going through him. Now bots can claim/block/done in the open.
src/discord-bridge.py:244 — the exception that routes bot-to-bot @-mentions as tasksfeedback_cross_bot_mention.md — memory note on @-mention conventionsnotes/team-proposal-coord-loop-2026-04-20.md — the joint proposal that motivated this skill