openclaw-channel-dmwork 0.6.0-dev.248385c8 → 0.6.0-dev.93ccd127

package/skills/dmwork-bot-api/SKILL.md

@@ -27,7 +27,8 @@ curl -X POST <apiUrl>/v1/bot/register \
 Response:
 ```json
 {
-  "robot_id": "xxx_bot",
+  "robot_id": "27ba6or9NU_bot",
+  "name": "My Bot",
   "im_token": "xxxxxx",
   "ws_url": "<wsUrl>",
   "api_url": "<apiUrl>",
@@ -59,42 +60,25 @@ After registering, send a greeting to your owner (DM to owner_uid) to confirm yo
 
 ### Method A: OpenClaw Plugin (Recommended — Real-time)
 
-Install the pre-built adapter as an OpenClaw extension for instant message delivery, real-time online status, and auto-reconnect.
+Install the pre-built adapter for instant message delivery, real-time online status, and auto-reconnect.
 
+**Install plugin:**
 ```bash
-# Install via npm (recommended)
-openclaw plugins install openclaw-channel-dmwork
+npx -y openclaw-channel-dmwork install
 ```
 
-Configure in `~/.openclaw/openclaw.json`:
-
-```json
-{
-  "channels": {
-    "dmwork": {
-      "botToken": "YOUR_BOT_TOKEN",
-      "apiUrl": "<apiUrl>"
-    }
-  }
-}
+**Single bot — bind to agent:**
+```bash
+npx -y openclaw-channel-dmwork bind --bot-token YOUR_BOT_TOKEN --api-url <apiUrl> --account-id <robot_id> --agent <agent_id>
 ```
 
-Multiple bots on one Gateway (multi-account):
-
-```json
-{
-  "channels": {
-    "dmwork": {
-      "apiUrl": "<apiUrl>",
-      "accounts": {
-        "bot-a": { "botToken": "TOKEN_A" },
-        "bot-b": { "botToken": "TOKEN_B" }
-      }
-    }
-  }
-}
+**All agents — one-click setup:**
+```bash
+npx -y openclaw-channel-dmwork quickstart --api-key uk_YOUR_KEY --api-url <apiUrl>
 ```
 
+The CLI automatically writes `~/.openclaw/openclaw.json` config and agent bindings. No manual config editing needed.
+
 ### Multi-Agent Setup Guide
 
 When one owner creates multiple bots (e.g. via BotFather /newbot), each bot can be connected to a separate AI Agent. Each bot gets its own accountId in the OpenClaw config with independent settings.
@@ -920,13 +904,10 @@ Each API Key is bound to a specific Space. When you run /quickstart in a Space,
 
 ### Quickstart Flow
 
-1. Get your User API Key from BotFather /quickstart command (key is bound to your current Space)
-2. Create a bot via POST /v1/user/bots
-3. Get the bot_token from the response
-4. Register the bot via POST /v1/bot/register with the bot_token
-5. Configure openclaw.json with the bot_token and apiUrl
-6. Set session.dmScope to "per-account-channel-peer"
-7. Verify the bot is online
+1. Get your User API Key from BotFather `/quickstart` command (key is bound to your current Space)
+2. Run `npx -y openclaw-channel-dmwork quickstart --api-key <key> --api-url <apiUrl>`
+3. The CLI automatically creates bots for all agents, writes config, and sends greetings
+4. Verify by sending a message to the bot in DMWork
 
 ### Endpoints
 
@@ -944,14 +925,16 @@ Each API Key is bound to a specific Space. When you run /quickstart in a Space,
 curl -X POST <apiUrl>/v1/user/bots \
   -H "Authorization: Bearer uk_YOUR_API_KEY" \
   -H "Content-Type: application/json" \
-  -d '{"name": "My Bot", "username": "mybot", "description": "A helpful assistant"}'
+  -d '{"name": "My Bot", "description": "A helpful assistant"}'
 ```
 
+Note: Bot ID (robot_id) is auto-generated by the server. The username field is deprecated and ignored if provided.
+
 Response:
 ```json
 {
-  "robot_id": "mybot_bot",
-  "username": "mybot_bot",
+  "robot_id": "27ba6or9NU_bot",
+  "username": "27ba6or9NU_bot",
   "name": "My Bot",
   "description": "A helpful assistant",
   "bot_token": "bf_xxxxxxxx"