Individual skill

peer-message

Bridges Claude Code and Codex sessions when native tools can't reach the target. Use for 跨产品通信 / 脚本回帖 / 送达排查: cross-product messages, hooks or scripts posting to a session, verifying delivery (Held messages included), shared-work ownership, or an inbound peer assertion. Not for same-product or parent/subagent messaging (use native tools), spawning agents, moving full history, or cross-machine pairing (deprecated).

peer-message/SKILL.md

Read pinned source

Source commit 7c4d326ddd94d504e00e241ba49498e95160afbe

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,522
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 19,580 bytes
SKILL.mdcore · 19,580 bytes
SKILL.mdcore · 19,580 bytes
evals/evals.jsonasset · 2,703 bytes
hooks/hooks.jsonasset · 370 bytes
references/coordination-and-learning-loop.mddoc · 49,230 bytes
references/local-coordination.mddoc · 20,865 bytes
references/network-preview.mddoc · 7,621 bytes
references/official-feature.mddoc · 10,611 bytes
references/protocol-and-discovery.mddoc · 31,932 bytes
runtime/package-lock.jsonasset · 50,185 bytes
runtime/package.jsonruns · 313 bytes
scripts/codex_live.pyruns · 5,115 bytes
scripts/coordination.pyruns · 39,508 bytes
scripts/install_native_guard.pyruns · 2,498 bytes
scripts/native-guard.shruns · 608 bytes
scripts/native_guard.pyruns · 6,311 bytes
scripts/network-agentpair.mjsruns · 5,190 bytes
scripts/network-common.mjsruns · 5,552 bytes
scripts/network-daemon.mjsruns · 15,972 bytes
scripts/network-host.mjsruns · 4,985 bytes
scripts/network-state.mjsruns · 5,251 bytes
scripts/peer-network.mjsruns · 7,601 bytes
scripts/peer.pyruns · 86,474 bytes
tests/fixtures/coordination_v117.pyruns · 17,196 bytes
tests/test_cli_error_receipts.pyruns · 8,046 bytes
tests/test_codex_live.pyruns · 7,608 bytes
tests/test_coord_actor.pyruns · 7,617 bytes
tests/test_coordination.pyruns · 15,879 bytes
tests/test_discovery_output.pyruns · 27,689 bytes
tests/test_native_guard.pyruns · 12,018 bytes
tests/test_network.mjsruns · 7,676 bytes
tests/test_peer.pyruns · 86,911 bytes
tests/test_receive_integrity.pyruns · 23,933 bytes
tests/test_state_coordination.pyruns · 18,569 bytes
tests/test_status_output.pyruns · 9,462 bytes

Read excerpt


# peer-message — 本机协调与通信补缺

对 Claude Code 与 Codex 使用同一条通信规则：先检查当前宿主实际暴露的通信工具及其目标范围；有工具发现入口时先查询原生工具。原生工具能到达目标，就直接使用其发现、发送、回传和等待机制，不另跑 `send/broadcast/verify/replies`。只有原生工具未覆盖的独立会话、跨产品目标或脚本回帖才使用本 Skill 的 transport。独立会话之间的任务归属、共享资源和请求生命周期由本 Skill 的 `coord` 管理，原生发送仍走原生工具；原生父子任务不增加这层登记。

不要用产品名、模型名、安装版本或安装包中的工具定义代替当前工具可用性。原生工具覆盖当前任务树，不代表能寻址任意独立 session；目标缺失或地址不明时先消歧。权限拒绝、Held、超时与发送结果不明都不是换通道的依据，也不要为了补缺修改权限或接收策略。

## 安装后的协调维护

独立会话开工、遇到归属冲突或申请共享资源窗口时，先读 [本地协调机制](references/local-coordination.md)，执行其中的状态查询、本人登记和请求处理。Agent 自行执行；不让用户另装 Fleet、建台账或逐条维护。`scripts/peer.py coord` 首次调用自动初始化本机共享状态，后续调用维护同一库，不需要常驻进程。任务状态在 Skill 包外，更新 Skill 不覆盖它。

先从明确任务引用和实际共享资源核对范围；已有负责人时直接定位该负责人，有疑点才定向问一次。空登记只表示尚未接入，陈旧登记只表示需要核验；二者都不授予执行权。开始或改变参与范围时登记，完成或交接时由本人释放，不把消息回执当成业务完成。

`send/broadcast` 自动经过同一去重记录。短时窗口问题使用稳定 `--topic`、`--kind request` 和实际有效期；同一待答事项即使换措辞也不会重复投递。原生跨会话发送用 `coord prepare` → 原生工具 → `coord commit`，只记录一次，不追加脚本发送。收到 `[peer-coordination: ...]` 时先用 `coord receive` 判断是否仍需处理，关联问题处理完用 `coord finish` 关闭；旧信封没有该字段时沿下面的语义分流，不猜有效期。