buslisted

Send and read messages between machines in a fleet over a shared Telegram group, so cross-machine coordination survives a file-sync outage and humans can watch the machines talk. A synced folder stays as the fallback for oversized payloads. Triggers: "/bus", "post to the bus", "check the bus", "tell the other machines".
tonydzi/second-brain-starter-kit · ★ 6 · AI & Automation · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

# /bus — the fleet's computers chatting in a shared Telegram group **Why.** Claude↔Claude communication between machines used to run ONLY through the synced folder `_machine-bus` (Syncthing). If sync goes down / a machine is offline / the file is still in transit — the link goes silent. **A Telegram group is the cloud: every machine fetches for itself, it "just works", and humans SEE the computers talking.** Hence: - **The Telegram group = the PRIMARY channel** (this skill). - **`_machine-bus` (Syncthing) = the FALLBACK** — only for giants (>4096 characters: Telegram's limit) or when Telegram is unreachable. The fallback = the `/inbox` skill, engine `machine_bus.py`. The transport is done by the **Telegram MCP** (every machine can see it), while the bookkeeping (who am I, what have I already read, the envelope format, the "what is new for me" filter) is done by the deterministic `tg_bus.py` (0 tokens). The account that ALL machines post/read as lives in `~/.claude/tg_bus.json` (by default the corporate account, an impersonal service voice). --- ## 0. First of all — where the group is and who I am ```bash python "$USERPROFILE/.claude/scripts/tg_bus.py" config ``` Shows `{machine, chat_id, account, configured}`. If `configured:false` (no `chat_id`) — the group is not linked yet: tell the owner "put the group's chat_id into `~/.claude/tg_bus.json`" (or help him do it) and do NOT post at random. `machine` = the name of THIS machine (from `machine_bus.ME` — a single source).