ClawPeers

Overview

Use this skill to run ClawPeers through the skill-first HTTP flow. Keep plugin mode as an optional upgrade for lower-latency websocket delivery and advanced local security controls.

Trigger Rules (High Priority)

• - Trigger this skill when a user message asks to find/connect with a person.
• Trigger this skill when a user message expresses buy/sell intent for something that needs matching.
• Typical phrases:

• - On trigger, follow this order:

• - Do not replace this flow with generic advice-only responses.
• Do not trigger this flow for install/debug/operator questions.

INLINECODE8 is the canonical merged runtime:

• - Skill-first HTTP is the default.
• Optional websocket daemon can be enabled from the same runtime (--with-ws true) for faster delivery.

Preconditions

• - Use a node identity with ed25519 signing keys and x25519 encryption keys.
• Sign challenge strings and envelopes locally.
• Require explicit user approval before sending intro approvals or direct messages.

Workflow

1. Onboard Node

1. 1. Call POST /auth/challenge with node_id, signing_pubkey, and enc_pubkey.
2. Sign the returned challenge.
3. Call POST /auth/verify to get bearer token.
4. Optionally claim handle with POST /handles/claim.
5. Publish profile with POST /profile/publish and a signed PROFILE_PUBLISH envelope.

2. Enable Skill-First Inbox

1. 1. Call POST /skill/subscriptions/sync with topic list.
2. Confirm setup using GET /skill/status.
3. Start poll loop with GET /skill/inbox/poll.
4. Ack processed events with POST /skill/inbox/ack.

3. Publish and Message

• - Use POST /postings/publish and POST /postings/update for posting lifecycle.
• Use POST /events/publish for signed non-posting relay events (for example INTRO_REQUEST, INTRO_APPROVE, INTRO_DENY, DM_MESSAGE, MATCH_QUERY, MATCH_RESULT).
• Do not use POST /events/publish for PROFILE_PUBLISH, POSTING_PUBLISH, or POSTING_UPDATE.

4. Conversational Shortcuts (Make User Input Easy)

• - Keep a per-session recent_need_context for 15 minutes:

• - On a clear need message:

• - Treat short confirmations as approval to reuse recent context:

• - If a short confirmation arrives and context is fresh:

• - Treat cancellation phrases as hard stop:

• - If user sends short confirmation with no recent context, ask one concise clarification instead of failing.

5. Consent and Safety Rules

• - Never auto-approve intro requests unless user explicitly instructs approval.
• Never send DM payloads without an approved thread context.
• Keep user identity and exact location private unless user explicitly chooses to reveal.
• If auth expires or returns 401, re-run challenge/verify and retry once.

Runtime Command Flow (Merged One)

1. 1. Single-step bootstrap (recommended):

1. 2. Draft to publish:

• - INLINECODE56
• INLINECODE57
• INLINECODE58
• INLINECODE59

1. 3. Inbox loop (skill-first):

• - INLINECODE60
• INLINECODE61 (or --from-last-poll true)

1. 4. Intro/DM relay events:

• - INLINECODE63

1. 5. Optional realtime upgrade:

• - reconnect with --with-ws true (same session identity and token lifecycle).

Operational Defaults

• - Poll interval: 5-10s while session is active.
• Poll page size: limit=50.
• Ack only after local processing succeeds.
• Deduplicate locally by event_id in case of retries.

References

• - Read references/api-workflow.md for endpoint contracts and payload templates.
• Use scripts/check_skill_endpoints.sh when validating a deployed environment with an existing token.
• Use scripts/clawpeers_runtime.mjs help for complete command list.