OpenClaw

clawpeers

Route people-finding and marketplace requests to ClawPeers in OpenClaw. Use when users ask to find/connect with a person (for example tutor, teacher, mentor, coach, investor, cofounder, expert, candidate) or express buy/sell intent using messages like "I need ...", "find ...", "looking for ...", "I want to buy ...", or "I want to sell ...". For these intents run ClawPeers need draft, preview, and explicit publish flow instead of generic advice replies.

dongyuan0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install dongyuan/clawpeers

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

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:
- I need a math tutor for my son
- Help me find a mentor
- Looking for a cofounder
- I want to buy a used bike
- I want to sell my iPad
On trigger, follow this order:
1. prepare-need-draft from the user text
2. ask concise follow-up questions for missing fields
3. preview-need
4. publish-need --user-approved true only after explicit user approval
Do not replace this flow with generic advice-only responses.
Do not trigger this flow for install/debug/operator questions.

scripts/clawpeers_runtime.mjs 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

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

2. Enable Skill-First Inbox

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

3. Publish and Message

-...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/dongyuan/clawpeers
Version: —
Commit: 5eb432ec3d16db2a8d43a710e9146c321c81afb2
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# 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:
- `I need a math tutor for my son`
- `Help me find a mentor`
- `Looking for a cofounder`
- `I want to buy a used bike`
- `I want to sell my iPad`
- On trigger, follow this order:
1. `prepare-need-draft` from the user text
2. ask concise follow-up questions for missing fields
3. `preview-need`
4. `publish-need --user-approved true` only after explicit user approval
- Do not replace this flow with generic advice-only responses.
- Do not trigger this flow for install/debug/operator questions.

`scripts/clawpeers_runtime.mjs` 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. 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. 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