bot2bot-post by sonichi

Decision brief

What it does—and where it fits

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 routes the post to the other bot's loop.

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

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability 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/bot2bot-post"

Safe inspection promptEditorial

Inspect the Agent Skill "bot2bot-post" from https://github.com/sonichi/sutando/blob/6a8f0fccd32e5aa620a3572c8885544f144bb6fe/skills/bot2bot-post/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

01
Usage
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?"
claim — "I'm taking this work, ETA X"blocked — "I'm stuck on X, need eyes"done — "shipped X, FYI"
02
Configuration
Channel: resolved from $CLAUDECONFIGDIR/channels/discord/access.json — pick the groups entry tagged {"role": "bot2bot", ...}, fallback to any entry with value true.
Channel: resolved from $CLAUDECONFIGDIR/channels/discord/access.json — pick the groups entry tagged {"role": "bot2bot", ...}, fallback to any entry with value true.Token: DISCORDBOTTOKEN read from $CLAUDECONFIGDIR/channels/discord/.env.Other bot ID: picked from the allowFrom list, excluding this bot's own ID (fetched via Discord /users/@me).
03
Why
Before this skill: bot A could reply in a task-triggered channel (existing pendingreplies path) and DM the owner (pollproactive), 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/bl…
Before this skill: bot A could reply in a task-triggered channel (existing pendingreplies path) and DM the owner (pollproactive), but had no way to initiate a channel post. That made cross-bot coord invisible to Chi and…

Permission review

Static risk signals and limitations

Runs scripts

medium · line 8

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

python3 skills/bot2bot-post/post.py <kind> <text>

Runs scripts

medium · line 20

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

python3 skills/bot2bot-post/post.py claim "refactor task-bridge task-file schema ETA 20m"

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	61/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	359	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: sonichi/sutando
Skill path: skills/bot2bot-post/SKILL.md
Commit: 6a8f0fccd32e5aa620a3572c8885544f144bb6fe
License: MIT
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

Bot-to-Bot Post

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.

Usage

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?"

Configuration

Channel: resolved from $CLAUDE_CONFIG_DIR/channels/discord/access.json — pick the groups entry tagged {"role": "bot2bot", ...}, fallback to any entry with value true.
Token: DISCORD_BOT_TOKEN read from $CLAUDE_CONFIG_DIR/channels/discord/.env.
Other bot ID: picked from the allowFrom list, excluding this bot's own ID (fetched via Discord /users/@me).

Why

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.

What it does—and where it fits

Best for

Not for

Platform support, with evidence labels

Inspect first. Install second.

What the source asks the agent to do

Usage

Configuration

Why

Static risk signals and limitations

Runs scripts

Runs scripts

Why each signal appears

Provenance and original SKILL.md

Bot-to-Bot Post

Usage

Configuration

Why

See also