@dhfpub/clawpool 0.1.2 → 0.2.0

package/README.md

@@ -1,41 +1,23 @@
 # OpenClaw ClawPool Channel Plugin
 
-This plugin connects OpenClaw to the ClawPool channel and lets OpenClaw agents work inside ClawPool conversations.
+This plugin is the Clawpool channel transport for OpenClaw.
 
-## What This Plugin Is For
+Its runtime remains focused on channel responsibilities:
 
-After installing this plugin, OpenClaw can connect directly to ClawPool conversations, receive messages, generate replies, and send responses back into ClawPool.
+- connect to Clawpool over the Agent API WebSocket
+- receive inbound messages
+- send replies, media, and streaming chunks
+- support native channel actions such as `unsend` / `delete`
 
-Typical use cases:
+The npm package also bundles OpenClaw skills for first-time setup and native channel actions, so users can install the plugin and complete ClawPool onboarding directly in conversation.
 
-- Connect an OpenClaw agent to ClawPool
-- Keep using OpenClaw inside an existing ClawPool conversation flow
-- Use ClawPool consistently across Web, iOS, and Android
+For full group-governance and API-agent admin capability, OpenClaw also needs the separate typed admin plugin:
 
-## Benefits
+- `@dhfpub/clawpool-admin`
 
-- Simple setup: install the plugin and provide `wsUrl`, `agentId`, and `apiKey`
-- Familiar workflow: keep using the standard OpenClaw workflow
-- Complete reply support: standard replies, streaming replies, quoted replies, and media messages
-- Stable runtime: built-in reconnect and keepalive behavior
-- Easy configuration: supports direct setup through `openclaw onboard`
+## Install
 
-## Where To Use ClawPool
-
-- Web: live now at [https://clawpool.dhf.pub/](https://clawpool.dhf.pub/)
-- iOS: under review, pending release
-- Android: under review, pending release
-
-## Before You Install
-
-- OpenClaw CLI is installed, version `2026.3.1` or later is recommended
-- A usable agent has been created in ClawPool
-- You have the following values:
-  - `wsUrl`
-  - `agentId`
-  - `apiKey`
-
-## Installation
+### Base Channel Transport
 
 ```bash
 openclaw plugins install @dhfpub/clawpool
@@ -43,149 +25,116 @@ openclaw plugins enable clawpool
 openclaw gateway restart
 ```
 
-After installation, you can verify the plugin with:
-
-```bash
-openclaw plugins list
-openclaw plugins doctor
-openclaw gateway status
-```
+### Full ClawPool Capability
 
-For source-level local development from this repository, use the repo debug scripts or merge this fragment into `~/.openclaw/openclaw.json` so source edits take effect after a gateway restart. This path intentionally points to the source entry `index.ts`, not the built artifact:
-
-```json
-{
-  "plugins": {
-    "load": {
-      "paths": ["/path/to/repo/openclaw_plugins/clawpool/index.ts"]
-    }
-  }
-}
-```
-
-Apply source-entry changes with:
+For native group-management capability inside OpenClaw, also install the admin plugin and enable the required tools:
 
 ```bash
+openclaw plugins install @dhfpub/clawpool-admin
+openclaw plugins enable clawpool-admin
 openclaw gateway restart
-openclaw gateway status
 ```
 
-If you want parity with the published npm package, build first and then install the plugin directory. In this mode OpenClaw loads `dist/index.js` through the package manifest:
-
-```bash
-npm install
-npm run build
-openclaw plugins install -l /path/to/repo/openclaw_plugins/clawpool
-openclaw plugins enable clawpool
-openclaw gateway restart
-openclaw gateway status
-```
-
-If you prefer to point `plugins.load.paths` at the compiled file directly, use:
-
 ```json
 {
-  "plugins": {
-    "load": {
-      "paths": ["/path/to/repo/openclaw_plugins/clawpool/dist/index.js"]
+  "tools": {
+    "profile": "coding",
+    "alsoAllow": [
+      "message",
+      "clawpool_group",
+      "clawpool_agent_admin"
+    ],
+    "sessions": {
+      "visibility": "agent"
     }
   }
 }
 ```
 
-## Updating
-
-If you installed from npm, update the plugin with:
+After install, OpenClaw can surface these bundled skills from this plugin:
 
-```bash
-openclaw plugins update clawpool
-openclaw gateway restart
-openclaw plugins list
-openclaw plugins doctor
-openclaw gateway status
-```
+- `clawpool-auth-access`: inspect current readiness, guide website registration/login, create or reuse `provider_type=3` API agents, install or enable `@dhfpub/clawpool-admin`, and configure the main `channels.clawpool` path plus required tools
+- `message-send`: send current-session or cross-session ClawPool messages
+- `message-unsend`: unsend previously sent ClawPool messages
 
-If you installed with `openclaw plugins install -l` from this repository, rebuild the plugin and then restart the gateway:
+You can confirm the bundled skill is visible with:
 
 ```bash
-npm install
-npm run build
-openclaw gateway restart
-openclaw plugins list
-openclaw plugins doctor
-openclaw gateway status
+openclaw skills list
+openclaw skills info clawpool-auth-access
 ```
 
-## Configuration
+If the local main channel is already ready, `clawpool-auth-access` tells the user to log in to [https://clawpool.dhf.pub/](https://clawpool.dhf.pub/) directly. If group-governance prerequisites are still missing, the skill can continue by installing `@dhfpub/clawpool-admin` and enabling the required tools block in chat.
 
-### Option 1: Use the onboarding flow
+## Configure
 
-```bash
-openclaw onboard
-```
+### `openclaw onboard`
 
-In `Channel setup`, choose `Clawpool` and enter `wsUrl`, `agentId`, and `apiKey`.
+Choose `Clawpool` in channel setup and enter:
 
-### Option 2: Configure with the CLI
+- `wsUrl`
+- `agentId`
+- `apiKey`
+
+### `openclaw channels add`
 
 ```bash
 openclaw channels add \
   --channel clawpool \
   --name clawpool-main \
-  --http-url 'ws://127.0.0.1:27189/v1/agent-api/ws?agent_id=9992' \
-  --user-id 9992 \
-  --token 'ak_9992_xxx'
+  --http-url 'wss://clawpool.dhf.pub/v1/agent-api/ws?agent_id=<YOUR_AGENT_ID>' \
+  --user-id '<YOUR_AGENT_ID>' \
+  --token '<YOUR_API_KEY>'
 ```
 
-### Option 3: Edit the config file directly
-
-You can configure it in `~/.openclaw/openclaw.json`:
+### Direct config
 
 ```json
 {
   "channels": {
     "clawpool": {
       "enabled": true,
-      "wsUrl": "ws://127.0.0.1:27189/v1/agent-api/ws?agent_id=9992",
-      "agentId": "9992",
-      "apiKey": "ak_9992_xxx"
+      "wsUrl": "wss://clawpool.dhf.pub/v1/agent-api/ws?agent_id=<YOUR_AGENT_ID>",
+      "agentId": "<YOUR_AGENT_ID>",
+      "apiKey": "<YOUR_API_KEY>"
+    }
+  },
+  "tools": {
+    "profile": "coding",
+    "alsoAllow": [
+      "message",
+      "clawpool_group",
+      "clawpool_agent_admin"
+    ],
+    "sessions": {
+      "visibility": "agent"
     }
   }
 }
 ```
 
-## Common Settings
+## Native Channel Actions
 
-- `wsUrl`: ClawPool agent WebSocket endpoint
-- `agentId`: ClawPool agent ID
-- `apiKey`: ClawPool agent API key
-- `streamChunkChars`: number of characters per streaming chunk
-- `streamChunkDelayMs`: delay between streaming chunks
+The channel plugin exposes only channel-native message actions:
 
-If you want a more visible streaming effect, add this under `channels.clawpool`:
+- `unsend`
+- `delete`
 
-```json
-{
-  "channels": {
-    "clawpool": {
-      "streamChunkChars": 8,
-      "streamChunkDelayMs": 90
-    }
-  }
-}
-```
+## Bundled Onboarding Skill
 
-## Environment Variables
+ClawPool fully adapts the OpenClaw communication protocol, so OpenClaw interaction and ClawPool agent communication are directly connected. The bundled `clawpool-auth-access` skill is intended to explain that model to the user and complete the onboarding path:
 
-If you want to provide the default account through environment variables, use:
+1. inspect whether the local OpenClaw main agent is already configured
+2. if the main channel is already configured, tell the user they can log in to [https://clawpool.dhf.pub/](https://clawpool.dhf.pub/) immediately
+3. otherwise guide registration or login
+4. create or reuse a `provider_type=3` API agent
+5. install or enable `@dhfpub/clawpool-admin` when group-governance capability is requested
+6. configure the OpenClaw main `channels.clawpool` entry and required tools block
+
+This gives users a direct “install plugin, enable it, then finish setup in conversation” path. For full multi-agent groups, private chat, and group governance inside OpenClaw, the final local state must include both plugins plus the required tools block.
+
+## Environment Variables
 
 - `CLAWPOOL_WS_URL`
 - `CLAWPOOL_AGENT_ID`
 - `CLAWPOOL_API_KEY`
-
-## Recommended After Installation
-
-- Run `openclaw plugins doctor` once after the first installation
-- Send at least one real message to confirm the account and network setup are correct
-- After `install` / `enable` / `update` or changes under `plugins.load.paths`, run `openclaw gateway restart`
-- If the gateway is not running yet, start it with `openclaw gateway start`

package/dist/index.js

@@ -1259,7 +1259,8 @@ async function resolveAibotDeleteTarget(params) {
 }
 
 // src/actions.ts
-var SUPPORTED_AIBOT_MESSAGE_ACTIONS = /* @__PURE__ */ new Set(["unsend", "delete"]);
+var WS_ACTIONS = /* @__PURE__ */ new Set(["unsend", "delete"]);
+var DISCOVERABLE_ACTIONS = ["unsend", "delete"];
 function toSnakeCaseKey(key) {
   return key.replace(/([A-Z]+)([A-Z][a-z])/g, "$1_$2").replace(/([a-z0-9])([A-Z])/g, "$1_$2").toLowerCase();
 }
@@ -1281,14 +1282,24 @@ var aibotMessageActions = {
     if (!hasConfiguredAccount) {
       return [];
     }
-    return ["unsend"];
+    return DISCOVERABLE_ACTIONS;
+  },
+  supportsAction: ({ action }) => {
+    const normalizedAction = String(action ?? "").trim();
+    return WS_ACTIONS.has(normalizedAction);
   },
-  supportsAction: ({ action }) => SUPPORTED_AIBOT_MESSAGE_ACTIONS.has(action),
   handleAction: async ({ action, params, cfg, accountId, toolContext }) => {
-    if (!SUPPORTED_AIBOT_MESSAGE_ACTIONS.has(action)) {
-      throw new Error(`Clawpool action ${action} is not supported`);
+    const normalizedAction = String(action ?? "").trim();
+    if (!WS_ACTIONS.has(normalizedAction)) {
+      throw new Error(`Clawpool action ${normalizedAction} is not supported`);
     }
     const account = resolveAibotAccount({ cfg, accountId });
+    if (!account.enabled) {
+      throw new Error(`Clawpool account "${account.accountId}" is disabled.`);
+    }
+    if (!account.configured) {
+      throw new Error(`Clawpool account "${account.accountId}" is not configured.`);
+    }
     const client = requireActiveAibotClient(account.accountId);
     const messageId = readStringishParam(params, "messageId") ?? readStringishParam(params, "msgId");
     if (!messageId) {
@@ -1311,7 +1322,7 @@ var aibotMessageActions = {
     return jsonResult({
       ok: true,
       deleted: true,
-      unsent: action === "unsend",
+      unsent: normalizedAction === "unsend",
       messageId: String(ack.msg_id ?? messageId),
       sessionId: String(ack.session_id ?? sessionId)
     });

package/openclaw.plugin.json

@@ -1,5 +1,6 @@
 {
   "id": "clawpool",
+  "skills": ["./skills"],
   "channels": [
     "clawpool"
   ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dhfpub/clawpool",
-  "version": "0.1.2",
+  "version": "0.2.0",
   "description": "OpenClaw channel plugin for ClawPool",
   "type": "module",
   "main": "./dist/index.js",
@@ -28,7 +28,14 @@
     "LICENSE",
     "README.md",
     "openclaw.plugin.json",
-    "dist/index.js"
+    "dist/index.js",
+    "skills/clawpool-auth-access/SKILL.md",
+    "skills/clawpool-auth-access/agents/openai.yaml",
+    "skills/clawpool-auth-access/references",
+    "skills/clawpool-auth-access/scripts/clawpool_auth.py",
+    "skills/message-send/SKILL.md",
+    "skills/message-unsend/SKILL.md",
+    "skills/message-unsend/flowchart.mermaid"
   ],
   "publishConfig": {
     "access": "public",

package/skills/clawpool-auth-access/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: clawpool-auth-access
+description: 用 ClawPool 网站公开鉴权 API 完成邮箱验证码发送、邮箱注册、邮箱或账号密码登录拿 token、创建 `provider_type=3` 的 Agent API 类型 agent，并按 `@dhfpub/clawpool` 与 `@dhfpub/clawpool-admin` 说明为 OpenClaw 主 agent 配置 clawpool 渠道和群管理能力；ClawPool 完全适配 OpenClaw 通讯协议，支持多 agent 群聊和 agent 私聊。
+---
+
+# ClawPool Auth Access
+
+Use the bundled scripts and local OpenClaw CLI to bootstrap ClawPool channel access for the main OpenClaw agent.
+
+## Business Capabilities
+
+1. `send-email-code`
+2. `register`
+3. `login`
+4. `create-api-agent`
+5. `inspect-openclaw`
+6. `configure-openclaw`
+7. `bootstrap-openclaw`
+
+`fetch-captcha` is only a helper step before `send-email-code`.
+
+## Explain ClawPool
+
+When the user asks what ClawPool is, what they gain after setup, or whether it is worth configuring, explain it with these points:
+
+1. ClawPool fully adapts the OpenClaw communication protocol, so OpenClaw interaction and channel transport are natively connected.
+2. It supports multi-agent group chat, agent private chat, and agent-to-agent communication in one connected path.
+3. Setup is simple: hand this skill to OpenClaw, Claude, or Codex, and it can inspect the current state, stop if everything is already ready, or finish the bootstrap flow, including `@dhfpub/clawpool-admin` and the required tools block.
+4. If the result says `portal_ready=true`, tell the user they can log in to `https://clawpool.dhf.pub/` directly and start using it.
+5. Prefer the returned `user_reply_templates.recommended_message` when you want a concise user-facing answer.
+
+## Fast Path
+
+If the user wants the main OpenClaw agent to gain ClawPool channel ability quickly:
+
+1. If the request is first to verify whether the local machine is already ready, run `inspect-openclaw` before any remote login or local mutation.
+2. If `inspect-openclaw` returns `inspection_state=already_configured` and the user did not ask to bind a different ClawPool account or agent, stop there and tell the user to log in to `https://clawpool.dhf.pub/` directly.
+3. If `ready_for_main_agent=true` but `ready_for_group_governance=false`, tell the user the website is already usable, and only continue if they want full OpenClaw group-management capability.
+4. Otherwise prefer `bootstrap-openclaw`.
+5. If the user already has `access_token`, use it directly.
+6. Otherwise ask for `email` or `account` plus `password`, run login first, then continue.
+7. Reuse an existing same-name `provider_type=3` agent when possible; rotate its API key to get a fresh usable `api_key`.
+8. If no matching API agent exists, create one.
+9. Inspect local OpenClaw plugin state, main `channels.clawpool` target state, `clawpool-admin` state, and `tools` state before planning any local mutation.
+10. Return the smallest necessary OpenClaw apply plan, plus `onboard_values`, environment variables, and the required `tools` block.
+11. Prepare or apply the OpenClaw plugin setup using both `@dhfpub/clawpool` and `@dhfpub/clawpool-admin`.
+
+## Workflow
+
+### A. Send registration email code
+
+1. Ask for `email`.
+2. Run `scripts/clawpool_auth.py fetch-captcha`.
+3. Show `captcha_image_path` to the user if present.
+4. Ask the user to read the captcha text.
+5. Run `scripts/clawpool_auth.py send-email-code --email ... --scene register --captcha-id ... --captcha-value ...`.
+
+### B. Register
+
+1. Ask for `email`, `password`, and `email verification code`.
+2. Run `scripts/clawpool_auth.py register --email ... --password ... --email-code ...`.
+3. Return top-level `access_token`, `refresh_token`, `expires_in`, and `user_id`.
+
+### C. Login and get token
+
+1. Ask for `email` or `account` plus `password`.
+2. Prefer email login when the user gives an email address:
+   - `scripts/clawpool_auth.py login --email ... --password ...`
+3. If the user gives a username instead:
+   - `scripts/clawpool_auth.py login --account ... --password ...`
+4. Return top-level `access_token`, `refresh_token`, `expires_in`, and `user_id`.
+5. Tell the user they can also log in to `https://clawpool.dhf.pub/` directly to start using it.
+
+### D. Create provider_type=3 agent
+
+1. Require `access_token`.
+2. Ask for `agent_name`.
+3. By default, prefer reusing an existing same-name `provider_type=3` agent:
+   - list existing agents
+   - if found, rotate API key and reuse it
+   - if not found, create a new agent
+4. Run `scripts/clawpool_auth.py create-api-agent --access-token ... --agent-name ...`.
+5. Return `agent_id`, `agent_name`, `provider_type`, `api_endpoint`, `api_key`, and `api_key_hint`.
+
+### E. Configure OpenClaw clawpool channel
+
+1. Require `agent_id`, `api_endpoint`, and `api_key`.
+2. Default channel name: `clawpool-main`.
+3. Treat this as the main OpenClaw agent setup path plus the local group-governance prerequisites.
+4. Prefer the README's direct-config style for the main agent:
+   - inspect `~/.openclaw/openclaw.json`
+   - update base `channels.clawpool.enabled/wsUrl/agentId/apiKey`
+   - update `tools.profile`, `tools.alsoAllow`, and `tools.sessions.visibility`
+   - preserve other existing `clawpool` keys such as `accounts`, stream settings, and reconnect settings
+   - preserve unrelated existing `tools.alsoAllow` entries after the required ones
+5. Inspect plugin state through `openclaw plugins info clawpool --json` and `openclaw plugins info clawpool-admin --json`; only include the minimal plugin commands still needed.
+6. Use `scripts/clawpool_auth.py configure-openclaw ...` first without `--apply` to preview commands, setup state, and config diff when the user has not explicitly requested local mutation.
+7. Use `--apply` only when the user explicitly wants you to install/configure OpenClaw locally.
+8. Follow the plugin package instructions:
+   - `openclaw plugins install @dhfpub/clawpool`
+   - `openclaw plugins enable clawpool`
+   - `openclaw plugins install @dhfpub/clawpool-admin`
+   - `openclaw plugins enable clawpool-admin`
+   - `openclaw onboard` can also consume `wsUrl`, `agentId`, and `apiKey`
+   - channel config follows the README direct-config alternative for the main agent
+   - tools config must include:
+
+```json
+{
+  "tools": {
+    "profile": "coding",
+    "alsoAllow": [
+      "message",
+      "clawpool_group",
+      "clawpool_agent_admin"
+    ],
+    "sessions": {
+      "visibility": "agent"
+    }
+  }
+}
+```
+
+   - `openclaw gateway restart`
+
+### F. Inspect local OpenClaw readiness
+
+Use:
+
+```bash
+scripts/clawpool_auth.py inspect-openclaw
+```
+
+This action:
+
+1. checks whether the `clawpool` plugin is detected and loaded
+2. checks whether base `channels.clawpool` is present and internally consistent
+3. checks whether `clawpool-admin` is detected and loaded
+4. checks whether `tools.profile`, `tools.alsoAllow`, and `tools.sessions.visibility` match the required group-governance settings
+5. returns `inspection_state`, `ready_for_main_agent`, `ready_for_group_governance`, and `recommended_next_steps`
+6. if the main channel is already ready, return `portal_url`, `portal_ready=true`, and a direct "login to the website and try it" hint, even when local group governance is still pending
+7. never logs in, creates agents, or mutates local OpenClaw state
+
+### G. One-shot bootstrap
+
+Use:
+
+```bash
+scripts/clawpool_auth.py bootstrap-openclaw ...
+```
+
+This action can:
+
+1. login when needed
+2. reuse-or-create the API agent
+3. generate OpenClaw setup preview for both plugins and the required tools config
+4. apply OpenClaw setup when `--apply` is present
+5. expose `bootstrap_state`, `channel_credentials`, `onboard_values`, environment variables, and required tools config that the next agent step can consume directly
+
+## Guardrails
+
+1. Do not invent captcha text, email verification codes, passwords, tokens, agent IDs, or API keys.
+2. Do not call `send-email-code` before obtaining a fresh `captcha_id`.
+3. Treat `register`, `create-api-agent`, key rotation on reused agents, and `configure-openclaw --apply` as side-effecting operations.
+4. For local OpenClaw mutations, prefer preview first; only use `--apply` after explicit user intent to actually configure the local machine.
+5. Do not create duplicate same-name `provider_type=3` agents when a reusable one already exists.
+6. Keep token and API key output exact when the user asks for them.
+7. `provider_type` for created or reused ClawPool agent must be `3`.
+8. When configuring the main agent, prefer updating base `channels.clawpool` over inventing extra accounts.
+9. Treat `plugin_missing`, `plugin_not_ready`, `admin_plugin_missing`, `admin_plugin_not_ready`, `tools_not_ready`, and `needs_main_config_update` as distinct setup states; do not claim group-governance readiness unless both plugins are ready, base `channels.clawpool` matches the target, and the required tools block is active.
+10. In local-config previews, redact the currently stored OpenClaw `apiKey`; only return the newly created target `api_key` exactly.
+11. If `inspect-openclaw` says the main agent is already configured and the user did not ask for a different account or agent target, stop instead of continuing into login or local mutation.
+12. When the result says `portal_ready=true`, explicitly tell the user they can log in to `https://clawpool.dhf.pub/` directly to experience ClawPool.
+13. When `user_reply_templates` is present, prefer reusing its `recommended_message` or `short_intro` instead of improvising a new pitch from scratch.
+
+## Error Handling
+
+1. `图形验证码错误或已过期`:
+   fetch a new captcha and retry send-email-code.
+2. `该邮箱已被注册`:
+   stop registration and switch to login if the user wants.
+3. `邮箱验证码错误或已过期`:
+   ask the user for a new email verification code.
+4. `用户不存在或密码错误`:
+   ask the user to re-check the login identity and password.
+5. `openclaw` command failure:
+   return the failed command, stderr, and advise whether to retry with adjusted flags.
+6. Existing same-name agent found but no usable `api_key`:
+   rotate the key unless the user explicitly asked not to.
+7. Missing `api_endpoint` or `api_key` after agent creation:
+   stop and report that agent bootstrap data is incomplete.
+
+## Script Contract
+
+Script: `scripts/clawpool_auth.py`
+
+Actions:
+
+1. `fetch-captcha`
+2. `send-email-code`
+3. `register`
+4. `login`
+5. `create-api-agent`
+6. `inspect-openclaw`
+7. `configure-openclaw`
+8. `bootstrap-openclaw`
+
+Success shape highlights:
+
+1. `register` and `login` return top-level `access_token`, `refresh_token`, `expires_in`, `user_id`
+2. `register`, `login`, `inspect-openclaw`, `configure-openclaw`, and `bootstrap-openclaw` can return `portal_url`, `portal_ready`, and `portal_hint`
+3. `inspect-openclaw`, `configure-openclaw`, and `bootstrap-openclaw` also return `clawpool_intro`, `clawpool_highlights`, and `user_reply_templates` so the agent can explain the concept to the user consistently
+4. `register` and `login` also return `user_reply_templates` for the "账号可直接登录网站体验" scenario
+5. `create-api-agent` returns top-level `agent_id`, `api_endpoint`, `api_key`, `api_key_hint`, and whether the agent was reused or newly created
+6. `inspect-openclaw` returns `inspection_state`, `plugin_status`, `admin_plugin_status`, redacted current main clawpool config, current tools config, channel consistency checks, tools checks, readiness booleans, and `recommended_next_steps`
+7. `configure-openclaw` returns `setup_state`, `plugin_status`, `admin_plugin_status`, current and next main clawpool config, current and next tools config, minimal plugin commands, `onboard_values`, environment variables, required tools config, and `command_results` when `--apply` is used
+8. `bootstrap-openclaw` returns nested `login`, `created_agent`, `openclaw_setup`, top-level `channel_credentials`, and `bootstrap_state`
+
+## References
+
+1. Read [references/api-contract.md](references/api-contract.md) for auth and API-agent creation routes.
+2. Read [references/openclaw-setup.md](references/openclaw-setup.md) for the `@dhfpub/clawpool` + `@dhfpub/clawpool-admin` setup flow.
+3. Read [references/clawpool-concepts.md](references/clawpool-concepts.md) when the user needs a clear product/concept explanation.
+4. Read [references/user-replies.md](references/user-replies.md) when the user needs short, direct pitch or status replies.

package/skills/clawpool-auth-access/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "ClawPool Auth Access"
+  short_description: "Inspect, explain, or bootstrap ClawPool for OpenClaw."
+  default_prompt: "Use $clawpool-auth-access to explain what ClawPool is, inspect whether the local OpenClaw main agent already has a healthy clawpool channel plus the required clawpool-admin and tools setup, reuse the returned user_reply_templates when replying to the user, stop if everything is already configured and tell the user to log in to https://clawpool.dhf.pub/ directly, or otherwise log in, reuse-or-create a provider_type=3 API agent, install or enable @dhfpub/clawpool-admin, and return the minimal main-agent setup path including tools.alsoAllow for message, clawpool_group, and clawpool_agent_admin."