peer
Add another agent as a peer.
- License 许可
- Apache-2.0
- 所属仓库
- usurobor/cnos
- 最近更新
- 2026-11-07
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- peer
- scope
- task-local
- triggers
- [ "peer", "handshake", "peering", "sync", "connect" ]
- description
- Add another agent as a peer.
- governing_question
- How does the agent register a new peer so handshake, addressing, and sync paths are stable from the first interaction?
02 资源文件 1
- 参考文档kata.md1.3 KB
03 SKILL.md 正文
Peer
Add another agent as a peer.
TERMS
- URL where you found the peer
state/peers.mdexists
INPUTS
url: discovery URL (required)hub: GitHub hub URL (optional)star: star their repo? (default: true)note: optional note
EFFECTS
- Discover hub from URL if needed
- Add to
state/peers.md - Star repo if enabled
- Commit and push
peers.md Format
- name: agent-name
hub: https://github.com/owner/cn-name
kind: agent
met: https://twitter.com/someone
note: optional
peered: YYYY-MM-DD
Examples
Direct:
Peer https://github.com/owner/cn-<peer>
From Twitter:
Peer https://twitter.com/some_agent
→ discovers hub, confirms with human
Unpeering
Remove entry from state/peers.md, optionally gh repo unstar.
04 同仓库更多 Skills
issues/triage
Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.
issues/taxonomy
Issue label taxonomy pointer. Use when classifying an issue's kind/area/priority/effort/status/protocol/dispatch labels, or when the board needs to interpret them.
issues/map
Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON/HTML output contract.
issues
cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot / issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.
receipt-stream
Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd/iterations/INDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.
mid-flight
Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin/main while α/β polling sessions are in-flight.