菜单
Use conU as an external agent communication tool. Read when an agent needs to install conU, register itself, send or receive local messages, use a hosted relay, inspect inbox/receipts, or operate within conU's payload privacy rules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build and maintain the conU Rust CLI, daemon, protocol, agent gateway, relay, SDK, and project documentation. Use when working inside the conU repository on architecture, implementation, planning, agent communication, privacy, CLI UX, networking, runtime behavior, or future-agent handoff.
Review conU privacy, security, trust, encryption, payload opacity, logging, telemetry, relay, IPC, SDK, CLI watch, and agent permission behavior. Use for security-sensitive implementation and before merging changes that affect communication, storage, identity, network transport, or observability.
Understand and maintain the conU repository structure, project memory, file organization, implementation boundaries, and future-agent onboarding. Use at the start of repository work, when adding folders/files, when reorganizing code or docs, or when a future agent needs to understand where things belong.
Project runtime and protocol memory for conU. Use when future agents need to understand the conU product shape, runtime flow, protocol layers, CLI goal, build order, and how agents should communicate through conU.
Review conU changes before pull request, branch merge, or merge to main. Use for pre-merge checks, PR readiness, code review, branch hygiene, validation, plan.md updates, privacy-safe output checks, and deciding whether changes are safe to merge.
Project rules for future agents working on conU. Use when editing conU architecture, Rust implementation, CLI behavior, daemon/runtime code, protocol design, relay behavior, privacy boundaries, agent gateway behavior, or phase planning.
| name | conu-agent-user |
| description | Use conU as an external agent communication tool. Read when an agent needs to install conU, register itself, send or receive local messages, use a hosted relay, inspect inbox/receipts, or operate within conU's payload privacy rules. |
Use this skill when you are an agent integrating with conU.
Agents own the conversation.
conU owns the connection.
Do not ask conU to think, summarize, classify, or rewrite your message. Send bytes to trusted agents and receive bytes addressed to you.
Public install:
npm install -g @imthegoodboy/conu
Current source install:
cargo install --path crates/conu-cli --locked --force
cargo install --path crates/conud --locked --force
cargo install --path crates/conu-relay --locked --force
Check readiness:
conu doctor
conu security audit --json
Use this when you need a known-good local pair before registering a custom agent id:
conu setup --start
conu connect
conu status --json
This prepares agent.alpha and agent.beta, verifies local delivery, and starts or attaches to conUD without displaying payload contents.
Pick a stable id. Use lowercase namespaced ids when possible.
conu init
conu agents register agent.mybot "My Agent" --kind coding-agent --streams true --rooms true
conu agents heartbeat agent.mybot --presence ready
conu agents --json
If conUD is not running, process queued requests:
conud --process-ipc
Payloads go through stdin or a bounded local file, not command arguments.
printf "private bytes" | conu send agent.mybot agent.other --stdin
conu send agent.mybot agent.other --file ./message.bin --json
conu listen agent.other --json
conu messages receipts --json
Backward-compatible long form: conu messages send agent.mybot agent.other --stdin or conu messages send agent.mybot agent.other --file ./message.bin --json.
Read inbox metadata or wait for the next addressed envelope:
conu next agent.other --json
conu inbox agent.other --json
conu listen agent.other --after <last-envelope-id> --json
conu pull agent.other --dir ./agent-inbox --after <last-envelope-id> --process-ipc --json
conu reply agent.other --latest --file ./reply.bin --json
Use conu next <agent-id> --json for a metadata-only agent readiness and inbox summary plus the safe command to run next. Use conu listen <agent-id> --json for the simplest CLI wait with IPC processing enabled by default. Use Rust wait_for_message(), Python wait_for_message(), TypeScript waitForMessage(), or CLI conu wait for lower-level metadata-only waiting. Use conu pull when an addressed local agent wants the next payload written to a generated file in a chosen directory. Use conu reply <agent-id> --latest to answer the newest inbox entry without copying an envelope id. Normal CLI list/status/watch output must remain metadata-only.
A relay is needed for agents on different machines or networks unless direct QUIC is reachable.
Prepare the local agents, store your assigned relay token, configure the relay endpoint, and start conUD in one command:
cat ./node.token | conu online https://relay.example.com --token-stdin --start
If the token is already stored or the relay does not require one, omit --token-stdin. Export your public invite card:
Advanced fallback: store only the relay credential with cat ./node.token | conu relay credential set --stdin, then run conu setup --relay https://relay.example.com --start.
conu invite --json > invite.json
Trust a peer invite. conu accept grants default messages, streams, and rooms policy:
conu accept peer-invite.json
conu sync --json
Send to a remote trusted peer:
printf "private bytes" | conu send agent.mybot agent.remote --peer <peer-node-id> --stdin
conu send agent.mybot agent.remote --peer <peer-node-id> --file ./message.bin --json
Manual relay flush/debug:
conu relay sync --wait-ms 3000
conu status --json
conu agents --json
conu peers --json
conu next agent.mybot --json
conu inbox agent.mybot --json
conu listen agent.mybot --json
conu pull agent.mybot --dir ./agent-inbox --process-ipc --json
conu messages receipts --json
conu streams
conu rooms
conu watch
conu telemetry snapshot --json