bencode

Provision a NEW dedicated baton worker on the current macOS host — git clone a repo, register the worker, and start it under launchd so it persists. Use when the user says "在小龙虾上给 X 仓库/项目起一个专属 worker / 孵化一个新 worker / 起一个跑 <模型> 的 worker / provision a worker / spin up a worker for this repo". The new worker sits permanently in that repo's context (no re-briefing each task) and can run its own model. Run this ON the host where the worker should live (a host worker agent there) — it needs local launchctl, the repo filesystem, and a logged-in reclaude. To then hand it work, use the delegate skill. To take one DOWN, see "Teardown" below (manual).

Join or host a live multi-agent chat room ("channel") on the baton server so Claude Code sessions — on different machines/people — can talk in real time over plain HTTP. Each room is its own auth domain: the unguessable id is the capability, with a self-describing API (curl the room manifest for its purpose/rules, curl /channels/help for the protocol). Use when the user says "开个频道 / 拉个多方房间 / 让几个 Claude 一起聊 / 跟同事的 Claude 连一下 / 开个对讲 / join this channel / host a channel / 把这个连接贴进来 connect to this channel". Supersedes the 2-party `hotline`. Two modes: relay (human in the loop, default) and autopilot (let the agents talk, bounded).

Open a live Claude↔Claude back-channel between two separate Claude Code sessions on different machines/people. One side hosts and hands the other a short invite; both then relay messages in real time over baton's relay channel. Use when the user says "connect to my colleague's Claude / 跟同事的 Claude Code 连一下 / 开个对讲 / 让两个 Claude 聊一下 / join this hotline / host a hotline / 把这个连接贴进来 connect to this channel". Two modes: relay (human in the loop, default) and autopilot (let the two agents talk, bounded).

Triage the GitHub issue queue and fan it out to baton sessions — pull open issues with a queue label (default dispatch:queue), propose a grouping plan, get the user's confirmation, then create one session per group with a self-contained brief and mark the issues as taken. Use when the user says "/dispatch", "安排任务", "派单", "把队列里的 issue 派一下", "拉 issue 安排一下", or asks to plan/distribute the pending GitHub issues.

baton collaboration — pick up work (handle T-N / implement R-N), create and decompose Requirements/Tasks, report progress via comments, advance the state machines. Use when asked to "handle T-3", "implement R-2", "split this requirement into tasks", "report progress", "what tasks are there", "create/record a task for me" (建个任务 / 记个任务 / 帮我记下来下次做 / 下次继续 / don't lose this across sessions), or whenever collaboration records need creating/updating on baton. When a HUMAN asks to create or record a task to be remembered or picked up later, that is ALWAYS a baton Task (durable, shared, survives sessions) — never the session-local todo tools (TaskCreate etc.), which evaporate with the session.

Operate GitHub issues from the current repo via the gh CLI — list what's open, see who's working on what, view an issue with its discussion, create or edit issues, comment progress, claim or hand off, and drive the labeled lifecycle (in-progress → needs-verification → verified) to close. Use when asked "看看有哪些 issue / what's open", "我的盘子 / what's on my plate", "看下 #12 / show me issue 12", "评论一下 / comment on it", "建个 issue / file an issue", "这个不做了 / cancel it", "关掉 #12 / close it", "认领 / take this", "转给 X / hand it to X", or any direct issue operation. The GitHub track is independent of baton Requirement/Task (the baton skill) — the two never cross-link.

Dispatch work to ANOTHER baton worker — same project or any other project: list workers, open a session on a chosen worker, hand it a self-contained brief, and reply with the session link. Use when the user says "交给 X worker / 让强力 worker 来 / 看看有哪些 worker / 列一下所有项目的 worker / 在 baton 项目开个 session 干活 / delegate this to W-N", or when a task clearly exceeds this session's worker and a stronger worker exists.

Use when adding or changing what `spec` (spectrum) can introspect in a host repo — registering a new entity type in the catalog, wiring a collector to a new Prisma/Fastify/services/GitHub surface, promoting a roadmap type to active, or adjusting verify commands and anchors. Edit the host's spectrum.config.ts, not the @lesscap/spectrum engine. Triggers include "make spec show jobs/pages", "add an entity type", "wire a new collector", "spec doesn't list X".

Use when you need to know what a backend actually contains — its Prisma models, HTTP routes, registered services, or use-cases — and whether the live system (database, running app) matches the declared truth. Drives the `spec` CLI (spectrum). Triggers include "what models/routes/services exist", "is the DB in sync", "list the endpoints", "is the schema migrated", "what does this service expose", "introspect the system".

LLM-powered query layer for Logseq vaults. SQLite + FTS5 + jieba CJK tokenizer for sub-millisecond cross-vault search, backlinks, and TODO aggregation that Logseq desktop can't deliver at scale. Atomic file primitives (parse / page / journal / find-page) plus DB-backed queries (index / stats / search / backlinks / todos). All results are formatted as `logseq://` URLs so Cmd+Click opens the matching page directly in Logseq desktop. Trigger when the user mentions "logseq", "today's journal" / "今天日志", "find X notes" / "找 X 笔记", "in my notes" / "在我笔记里", searches for content, asks about TODOs/backlinks, or references a /add-dir'd directory containing logseq/config.edn. Writes go through Claude's Read/Edit tools directly on the .md files, not through this CLI.

Distill raw chat transcripts into durable, retrievable memory atoms. Use when asked to refine memory, organize past conversations, or consolidate the memory directory (triggers like "refine memory", "整理记忆", "提炼会话").

Learn English on the fly. Triggers when a message starts with the `en:` prefix. Commands — en: quick help / en:? analyze what was just discussed / en:a <text> analyze / en:save store to your dictionary / en:review harvest the session / en:off leave learning mode. Dictionary at $EN_DICT (default ~/.en/dictionary.md). Discovery mode proactively surfaces what's worth learning (unknown-unknowns).

Collaborate via a Feishu (Lark) chat from this Claude Code session. On session start, launch the WS monitor as a background process and subscribe to its stdout stream — every inbound Feishu message (p2p, group `@`-you, and ambient group chatter) arrives in this conversation as a live event. The user can also drive you directly ("ask the peer agent about X", "post a file to the group"). Triggers include: the user saying "feishu collab" / "start feishu" / "start rooma" / "开飞书协作" / "启动飞书协作", starting work in this project, the user asking to send/check Feishu messages, or new events arriving from the monitor.

Surface agent-produced files (markdown, code, images, HTML, PDF) to a human by launching the margin-loop local viewer in the browser. Use when the agent generates output a human should look at.

Build and query a knowledge graph over a markdown vault (e.g. brain2). Files-as-truth — the graph lives in plain JSON under <vault>/meta/kg/ (registry of hash↔path, a concept table, and per-document metadata), so it's diffable, hand-editable, and git-committable; the SQLite index and viewer are rebuildable layers on top. Trigger when the user says "知识图谱 / knowledge graph / 建图谱 / 抽实体关系 / 这篇笔记关联了什么 / X 和 Y 有什么关系 / 哪些论文属于 X / kg", or wants to extract entities & relations from their notes. Extraction is layered: L1 a concept table (controlled vocabulary), L2 per-document mentions/relations carrying verbatim source anchors. The LLM (you) reads files and emits metadata JSON; the CLI only does deterministic file IO + anchor validation.

AI agent collaboration on GitHub Issues. Use when the user asks "what work is open / list open issues", "what's on my plate", "create/close an issue", "assign this to @xxx / Claude Code / Helm", "what is @xxx working on", "who owns this", or anything about routing tasks. **All data goes through the gh CLI; multi-step logic (lint / verify / close) goes through relay.py. Never create local issue files (.relay/issues/*.yaml etc.).**