[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BMMK5W2JNXC4973PXKMTTS":3,"skill-same:01M7BMMK5W2JNXC4973PXKMTTS":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BMMK5W2JNXC4973PXKMTTS","zeroclaw",null,"Help users operate and interact with their ZeroClaw agent instance — through both the CLI (`zeroclaw` commands) and the REST\u002FWebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API, troubleshoot their ZeroClaw setup, build from source, or do anything involving the `zeroclaw` binary or its HTTP endpoints. Trigger this even if the user just says things like 'check my agent status', 'schedule a reminder', 'store this in memory', 'list my cron jobs', 'send a message to my bot', 'set up Telegram', 'build zeroclaw', or 'my bot is broken' — these are all ZeroClaw operations.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fzeroclaw\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: zeroclaw\ndescription: \"Help users operate and interact with their ZeroClaw agent instance — through both the CLI (`zeroclaw` commands) and the REST\u002FWebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API, troubleshoot their ZeroClaw setup, build from source, or do anything involving the `zeroclaw` binary or its HTTP endpoints. Trigger this even if the user just says things like 'check my agent status', 'schedule a reminder', 'store this in memory', 'list my cron jobs', 'send a message to my bot', 'set up Telegram', 'build zeroclaw', or 'my bot is broken' — these are all ZeroClaw operations.\"\n---\n\n# ZeroClaw Skill\n\nYou are helping a user operate their ZeroClaw agent instance. ZeroClaw is an autonomous agent runtime with a CLI and an HTTP\u002FWebSocket gateway.\n\nYour job is to understand what the user wants to accomplish and then **execute it** — run the command, make the API call, report the result. Do not just show commands for the user to copy-paste. Actually run them via the Bash tool and tell the user what happened. The only exception is destructive operations (clearing all memory, estop kill-all) where you should confirm first.\n\n## Adaptive Expertise\n\nPay attention to how the user talks. Someone who says \"can you hit the webhook endpoint with a POST\" is telling you they know what they're doing — be concise, skip explanations, just execute. Someone who says \"how do I make my bot remember things\" needs more context about what's happening under the hood.\n\nSignals of technical comfort: mentions specific endpoints, HTTP methods, JSON fields, talks about tokens\u002Fauth, uses CLI flags fluently, references config files directly.\n\nSignals of less familiarity: asks \"what does X do\", uses casual language about the bot\u002Fagent, describes goals rather than mechanisms (\"I want it to check something every morning\").\n\nDefault to a middle ground — brief explanation of what you're about to do, then do it. Dial up or down from there based on cues.\n\n## Discovery — Before You Act\n\nBefore running any ZeroClaw operation, make sure you know where things are:\n\n1. **Find the binary.** Search in this order:\n   - `which zeroclaw` (PATH)\n   - The current project's build output: `.\u002Ftarget\u002Frelease\u002Fzeroclaw` or `.\u002Ftarget\u002Fdebug\u002Fzeroclaw` — this is the right choice when the user is working inside the ZeroClaw source tree and may have local changes\n   - Common install locations: `~\u002F.cargo\u002Fbin\u002Fzeroclaw`, `~\u002FDownloads\u002Fzeroclaw-bin\u002Fzeroclaw`\n\n   If no binary is found anywhere, offer to build from source (see \"Building from Source\" below). If the user is a developer working on ZeroClaw itself, they'll likely want the local build — watch for cues like them editing source files, mentioning PRs, or being in the project directory.\n\n2. **Check if the gateway is running** (only needed for REST\u002FWebSocket operations). A quick `curl -sf http:\u002F\u002F127.0.0.1:42617\u002Fhealth` tells you. If it's not running and the user wants REST access, let them know and offer to start it (`zeroclaw gateway` or `zeroclaw daemon`).\n\n3. **Check auth status.** If the gateway requires pairing (`require_pairing = true` is the default), REST calls need a bearer token. Run `zeroclaw status` to see the current state, or check `~\u002F.zeroclaw\u002Fconfig.toml` for a stored token under `[gateway]`.\n\n4. **Discover the agent alias.** Every `zeroclaw agent` invocation requires `-a \u003Calias>` — there is no default agent. Read `~\u002F.zeroclaw\u002Fconfig.toml` and find the `[agents.\u003Calias>]` headers; that `\u003Calias>` is what the user means when they say \"my agent.\" If multiple agents exist, ask the user which one to target before invoking. The examples below use `\u003Calias>` as a placeholder for the alias you discovered.\n\nCache these findings for the conversation — don't re-discover every time.\n\n## Important: REPL Limitation\n\n`zeroclaw agent -a \u003Calias>` (interactive REPL) requires interactive stdin, which doesn't work through the Bash tool. When the user wants to chat with their agent, use single-message mode instead:\n\n```bash\nzeroclaw agent -a \u003Calias> -m \"the message\"\n```\n\nEach `-m` invocation is independent (no conversation history between calls). If the user needs multi-turn conversation, let them know they can run `zeroclaw agent -a \u003Calias>` directly in their terminal, or use the WebSocket endpoint for programmatic streaming.\n\n## First-Time Setup\n\nIf the user hasn't set up ZeroClaw yet (no `~\u002F.zeroclaw\u002Fconfig.toml` exists), guide them through quickstart:\n\n```bash\nzeroclaw quickstart                                              # Interactive — picks a provider + agent\nzeroclaw quickstart --model-provider ollama --model qwen2.5:7b   # Non-interactive\nzeroclaw config set channels.\u003Cname>.\u003Cfield>=\u003Cvalue>              # Configure a channel after quickstart\n```\n\nAfter quickstart, verify everything works:\n```bash\nzeroclaw status\nzeroclaw doctor\n```\n\nIf they already have a config but a channel is broken, edit just that channel's fields with `zeroclaw config set channels.\u003Cname>.\u003Cfield>=\u003Cvalue>` rather than re-running quickstart (quickstart leaves an existing config alone).\n\n## Building from Source\n\nIf the user wants to build ZeroClaw (or no binary is installed):\n\n```bash\ncargo build --release\n```\n\nThis produces `target\u002Frelease\u002Fzeroclaw`. For faster iteration during development, `cargo build` (debug mode) is quicker but produces a slower binary at `target\u002Fdebug\u002Fzeroclaw`.\n\nYou can also run directly without a separate build step:\n```bash\ncargo run --release -- \u003Csubcommand> [args]\n```\n\nBefore building, `cargo check` gives a quick compile validation without the full build.\n\n## Choosing CLI vs REST\n\nBoth surfaces can do most things. Rules of thumb:\n\n- **CLI is simpler** for one-off operations from the terminal. It handles auth internally and formats output nicely. Prefer CLI when the user is working locally.\n- **REST is needed** when the user is building an integration, scripting from another language, or accessing a remote ZeroClaw instance. Also needed for streaming (WebSocket, SSE).\n- If unclear, **default to CLI** — it's less setup.\n\n## Core Operations\n\n### Sending Messages\n\n**CLI:** `zeroclaw agent -a \u003Calias> -m \"your message here\"` — always use `-m` mode (not bare `zeroclaw agent -a \u003Calias>`) so it returns instead of blocking on the REPL.\n\n**REST:**\n```bash\ncurl -X POST http:\u002F\u002F127.0.0.1:42617\u002Fwebhook \\\n  -H \"Authorization: Bearer \u003Ctoken>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"message\": \"your message here\"}'\n```\nResponse: `{\"response\": \"...\", \"model\": \"...\"}`\n\n**WebSocket** (for streaming): connect to `ws:\u002F\u002F127.0.0.1:42617\u002Fws\u002Fchat?token=\u003Ctoken>`, send `{\"type\": \"message\", \"content\": \"...\"}`, receive `{\"type\": \"done\", \"full_response\": \"...\"}`.\n\n### System Status\n\nRun `zeroclaw status` to see provider, model, uptime, channels, memory backend. For deeper diagnostics: `zeroclaw doctor`.\n\n**REST:** `GET \u002Fapi\u002Fstatus` (same info as JSON), `GET \u002Fhealth` (no auth, quick ok\u002Fnot-ok).\n\n### Memory\n\nThe CLI can list, get, and clear memories but **cannot store** them directly. To store a memory:\n- Via agent: `zeroclaw agent -a \u003Calias> -m \"remember that my favorite color is blue\"`\n- Via REST: `POST \u002Fapi\u002Fmemory` with `{\"key\": \"...\", \"content\": \"...\", \"category\": \"core\"}`\n\n**CLI (read\u002Fdelete):**\n- `zeroclaw memory list` — list all entries\n- `zeroclaw memory list --category core --limit 10` — filtered\n- `zeroclaw memory get \"key-name\"` — get specific entry\n- `zeroclaw memory stats` — usage statistics\n- `zeroclaw memory clear --key \"prefix\" --yes` — delete entries (confirm with user first)\n\n**REST (full CRUD):**\n- `GET \u002Fapi\u002Fmemory` — list all (optional: `?query=search+text&category=core`)\n- `POST \u002Fapi\u002Fmemory` — store: `{\"key\": \"...\", \"content\": \"...\", \"category\": \"core\"}`\n- `DELETE \u002Fapi\u002Fmemory\u002F{key}` — delete entry\n\nCategories: `core`, `daily`, `conversation`, or any custom string.\n\n### Cron \u002F Scheduling\n\n**CLI:**\n- `zeroclaw cron list` — show all jobs\n- `zeroclaw cron add '0 9 * * 1-5' 'Good morning' --tz America\u002FNew_York` — recurring\n- `zeroclaw cron add-at '2026-03-11T10:00:00Z' 'Remind me'` — one-time at specific time\n- `zeroclaw cron add-every 3600000 'Check health'` — interval in ms\n- `zeroclaw cron once 30m 'Follow up'` — delay from now\n- `zeroclaw cron pause \u003Cid>` \u002F `zeroclaw cron resume \u003Cid>` \u002F `zeroclaw cron remove \u003Cid>`\n\n**REST:**\n- `GET \u002Fapi\u002Fcron` — list jobs\n- `POST \u002Fapi\u002Fcron` — add: `{\"name\": \"...\", \"schedule\": \"0 9 * * *\", \"command\": \"...\"}`\n- `DELETE \u002Fapi\u002Fcron\u002F{id}` — remove job\n\n### Tools\n\nTools are used automatically by the agent during conversations (shell, file ops, memory, browser, HTTP, web search, git, etc. — 30+ tools gated by security policy).\n\nTo see what's available: `GET \u002Fapi\u002Ftools` (REST) lists all registered tools with descriptions and parameter schemas.\n\n### Configuration\n\nEdit `~\u002F.zeroclaw\u002Fconfig.toml` directly, use `zeroclaw config set \u003Ckey>=\u003Cvalue>` for one field at a time, or delete `~\u002F.zeroclaw\u002F` and re-run `zeroclaw quickstart` for a fresh setup.\n\n**REST:**\n- `GET \u002Fapi\u002Fconfig` — get current config (secrets masked as `***MASKED***`)\n- `PUT \u002Fapi\u002Fconfig` — update config (send raw TOML as body, 1MB limit)\n\n### Providers & Models\n\n- `zeroclaw providers` — list all supported providers\n- `zeroclaw models list` — cached model catalog\n- `zeroclaw models refresh --all` — refresh from providers\n- `zeroclaw models set anthropic\u002Fclaude-sonnet-4-6` — set default model\n\nOverride per-message: `zeroclaw agent -a \u003Calias> -p anthropic --model claude-sonnet-4-6 -m \"hello\"`\n\n### Real-Time Events (SSE)\n\nREST only — useful for building dashboards or monitoring:\n```bash\ncurl -N -H \"Authorization: Bearer \u003Ctoken>\" http:\u002F\u002F127.0.0.1:42617\u002Fapi\u002Fevents\n```\nStreams JSON events: `llm_request`, `tool_call_start`, `tool_call`, `agent_start`, `agent_end`, `error`.\n\n### Cost Tracking\n\n`GET \u002Fapi\u002Fcost` — returns session\u002Fdaily\u002Fmonthly costs, token counts, per-model breakdown.\n\n### Emergency Stop\n\nConfirm with the user before running any estop command — these are disruptive.\n\n- `zeroclaw estop --level kill-all` — stop everything\n- `zeroclaw estop --level network-kill` — block all network\n- `zeroclaw estop --level tool-freeze --tool shell` — freeze specific tool\n- `zeroclaw estop status` — check current estop state\n- `zeroclaw estop resume --network` — resume\n\n### Gateway Lifecycle\n\n- `zeroclaw gateway` — start HTTP gateway (foreground)\n- `zeroclaw gateway -p 8080 --host 127.0.0.1` — custom bind\n- `zeroclaw daemon` — start gateway + channels + scheduler + heartbeat\n- `zeroclaw service install\u002Fstart\u002Fstop\u002Fstatus\u002Funinstall` — OS service management\n\n### Channels\n\nZeroClaw supports 21 messaging channels. To add one, you need to edit `~\u002F.zeroclaw\u002Fconfig.toml`. For example, to set up Telegram:\n\n```toml\n[channels]\ntelegram = true\n\n[channels_config.telegram]\nbot_token = \"your-bot-token-from-botfather\"\nallowed_users = [123456789]\n```\n\nThen restart the daemon. Check channel health with `zeroclaw channels doctor`.\n\nFor the full list of channels and their config fields, read `references\u002Fcli-reference.md` (Channels section).\n\n### Pairing (Authentication Setup)\n\nWhen `require_pairing = true` (default), REST clients need a bearer token:\n```bash\ncurl -X POST http:\u002F\u002F127.0.0.1:42617\u002Fpair -H \"X-Pairing-Code: \u003Ccode>\"\n```\nResponse includes `{\"token\": \"...\"}` — save this for subsequent requests.\n\n## Common Workflows\n\nHere are multi-step sequences you're likely to need:\n\n**\"Is my agent healthy?\"**\n1. Run `zeroclaw status` — check provider, model, channels\n2. Run `zeroclaw doctor` — check connectivity, diagnose issues\n3. If gateway needed: `curl -sf http:\u002F\u002F127.0.0.1:42617\u002Fhealth`\n\n**\"Set up a new channel\"**\n1. Read the current config: `cat ~\u002F.zeroclaw\u002Fconfig.toml`\n2. Add the channel config (edit the TOML)\n3. Restart: `zeroclaw service restart` (or restart daemon manually)\n4. Verify: `zeroclaw channels doctor`\n\n**\"Switch to a different model\"**\n1. Check available: `zeroclaw models list`\n2. Set it: `zeroclaw models set \u003Cprovider\u002Fmodel>`\n3. Verify: `zeroclaw status`\n4. Test: `zeroclaw agent -a \u003Calias> -m \"hello, what model are you?\"`\n\n## Gateway Defaults\n\n- **Port:** 42617\n- **Host:** 127.0.0.1\n- **Auth:** Pairing required (bearer token)\n- **Rate limits:** 60 webhook requests\u002Fmin, 10 pairing attempts\u002Fmin\n- **Body limit:** 64KB (1MB for config updates)\n- **Timeout:** 30 seconds\n- **Idempotency:** Optional `X-Idempotency-Key` header on `\u002Fwebhook` (300s TTL)\n- **Config location:** `~\u002F.zeroclaw\u002Fconfig.toml`\n\n## Reference Files\n\nFor the complete API specification with every endpoint, field, and edge case, read `references\u002Frest-api.md`.\n\nFor the full CLI command tree with all flags and options, read `references\u002Fcli-reference.md`.\n\nOnly load these when you need precise details beyond what's in this file — for most operations, the quick references above are sufficient.\n\n## Troubleshooting\n\n**\"zeroclaw: command not found\"** — Binary not in PATH. Check `.\u002Ftarget\u002Frelease\u002Fzeroclaw`, `~\u002F.cargo\u002Fbin\u002Fzeroclaw`, or build from source with `cargo build --release`.\n\n**\"Connection refused\" on REST calls** — Gateway isn't running. Start it with `zeroclaw gateway` or `zeroclaw daemon`.\n\n**\"Unauthorized\" (401\u002F403)** — Bearer token is missing or invalid. Re-pair via `POST \u002Fpair` with the pairing code, or check `~\u002F.zeroclaw\u002Fconfig.toml` for the stored token.\n\n**\"LLM request failed\" (500)** — Provider issue. Run `zeroclaw doctor` to check connectivity. Common causes: expired API key, provider outage, rate limiting on the provider side.\n\n**\"Too many requests\" (429)** — You're hitting ZeroClaw's rate limit. Back off — the response includes `retry_after` with the number of seconds to wait.\n\n**Agent not using tools \u002F acting limited** — Check autonomy settings in config.toml under `[autonomy]`. `level = \"read_only\"` disables most tools. Try `level = \"supervised\"` or `level = \"full\"`.\n\n**Memory not persisting** — Check `[memory]` config. If `backend = \"none\"`, nothing is stored. Switch to `\"sqlite\"` or `\"markdown\"`. Also verify `auto_save = true`.\n\n**Channel not responding** — Run `zeroclaw channels doctor` for the specific channel. Common issues: expired bot token, wrong allowed_users list, channel not enabled in `[channels]`.\n\nReport errors to the user with context appropriate to their expertise level. For beginners, explain what went wrong and suggest the fix. For experts, just show the error and the fix.\n","# ZeroClaw Skill\n\nYou are helping a user operate their ZeroClaw agent instance. ZeroClaw is an autonomous agent runtime with a CLI and an HTTP\u002FWebSocket gateway.\n\nYour job is to understand what the user wants to accomplish and then **execute it** — run the command, make the API call, report the result. Do not just show commands for the user to copy-paste. Actually run them via the Bash tool and tell the user what happened. The only exception is destructive operations (clearing all memory, estop kill-all) where you should confirm first.\n\n## Adaptive Expertise\n\nPay attention to how the user talks. Someone who says \"can you hit the webhook endpoint with a POST\" is telling you they know what they're doing — be concise, skip explanations, just execute. Someone who says \"how do I make my bot remember things\" needs more context about what's happening under the hood.\n\nSignals of technical comfort: mentions specific endpoints, HTTP methods, JSON fields, talks about tokens\u002Fauth, uses CLI flags fluently, references config files directly.\n\nSignals of less familiarity: asks \"what does X do\", uses casual language about the bot\u002Fagent, describes goals rather than mechanisms (\"I want it to check something every morning\").\n\nDefault to a middle ground — brief explanation of what you're about to do, then do it. Dial up or down from there based on cues.\n\n## Discovery — Before You Act\n\nBefore running any ZeroClaw operation, make sure you know where things are:\n\n1. **Find the binary.** Search in this order:\n   - `which zeroclaw` (PATH)\n   - The current project's build output: `.\u002Ftarget\u002Frelease\u002Fzeroclaw` or `.\u002Ftarget\u002Fdebug\u002Fzeroclaw` — this is the right choice when the user is working inside the ZeroClaw source tree and may have local changes\n   - Common install locations: `~\u002F.cargo\u002Fbin\u002Fzeroclaw`, `~\u002FDownloads\u002Fzeroclaw-bin\u002Fzeroclaw`\n\n   If no binary is found anywhere, offer to build from source (see \"Building from Source\" below). If the user is a developer working on ZeroClaw itself, they'll likely want the local build — watch for cues like them editing source files, mentioning PRs, or being in the project directory.\n\n2. **Check if the gateway is running** (only needed for REST\u002FWebSocket operations). A quick `curl -sf http:\u002F\u002F127.0.0.1:42617\u002Fhealth` tells you. If it's not running and the user wants REST access, let them know and offer to start it (`zeroclaw gateway` or `zeroclaw daemon`).\n\n3. **Check auth status.** If the gateway requires pairing (`require_pairing = true` is the default), REST calls need a bearer token. Run `zeroclaw status` to see the current state, or check `~\u002F.zeroclaw\u002Fconfig.toml` for a stored token under `[gateway]`.\n\n4. **Discover the agent alias.** Every `zeroclaw agent` invocation requires `-a \u003Calias>` — there is no default agent. Read `~\u002F.zeroclaw\u002Fconfig.toml` and find the `[agents.\u003Calias>]` headers; that `\u003Calias>` is what the user means when they say \"my agent.\" If multiple agents exist, ask the user which one to target before invoking. The examples below use `\u003Calias>` as a placeholder for the alias you discovered.\n\nCache these findings for the conversation — don't re-discover every time.\n\n## Important: REPL Limitation\n\n`zeroclaw agent -a \u003Calias>` (interactive REPL) requires interactive stdin, which doesn't work through the Bash tool. When the user wants to chat with their agent, use single-message mode instead:\n\n```bash\nzeroclaw agent -a \u003Calias> -m \"the message\"\n```\n\nEach `-m` invocation is independent (no conversation history between calls). If the user needs multi-turn conversation, let them know they can run `zeroclaw agent -a \u003Calias>` directly in their terminal, or use the WebSocket endpoint for programmatic streaming.\n\n## First-Time Setup\n\nIf the user hasn't set up ZeroClaw yet (no `~\u002F.zeroclaw\u002Fconfig.toml` exists), guide them through quickstart:\n\n```bash\nzeroclaw quickstart                                              # Interactive — picks a provider + agent\nzeroclaw quickstart --model-provider ollama --model qwen2.5:7b   # Non-interactive\nzeroclaw config set channels.\u003Cname>.\u003Cfield>=\u003Cvalue>              # Configure a channel after quickstart\n```\n\nAfter quickstart, verify everything works:\n```bash\nzeroclaw status\nzeroclaw doctor\n```\n\nIf they already have a config but a channel is broken, edit just that channel's fields with `zeroclaw config set channels.\u003Cname>.\u003Cfield>=\u003Cvalue>` rather than re-running quickstart (quickstart leaves an existing config alone).\n\n## Building from Source\n\nIf the user wants to build ZeroClaw (or no binary is installed):\n\n```bash\ncargo build --release\n```\n\nThis produces `target\u002Frelease\u002Fzeroclaw`. For faster iteration during development, `cargo build` (debug mode) is quicker but produces a slower binary at `target\u002Fdebug\u002Fzeroclaw`.\n\nYou can also run directly without a separate build step:\n```bash\ncargo run --release -- \u003Csubcommand> [args]\n```\n\nBefore building, `cargo check` gives a quick compile validation without the full build.\n\n## Choosing CLI vs REST\n\nBoth surfaces can do most things. Rules of thumb:\n\n- **CLI is simpler** for one-off operations from the terminal. It handles auth internally and formats output nicely. Prefer CLI when the user is working locally.\n- **REST is needed** when the user is building an integration, scripting from another language, or accessing a remote ZeroClaw instance. Also needed for streaming (WebSocket, SSE).\n- If unclear, **default to CLI** — it's less setup.\n\n## Core Operations\n\n### Sending Messages\n\n**CLI:** `zeroclaw agent -a \u003Calias> -m \"your message here\"` — always use `-m` mode (not bare `zeroclaw agent -a \u003Calias>`) so it returns instead of blocking on the REPL.\n\n**REST:**\n```bash\ncurl -X POST http:\u002F\u002F127.0.0.1:42617\u002Fwebhook \\\n  -H \"Authorization: Bearer \u003Ctoken>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"message\": \"your message here\"}'\n```\nResponse: `{\"response\": \"...\", \"model\": \"...\"}`\n\n**WebSocket** (for streaming): connect to `ws:\u002F\u002F127.0.0.1:42617\u002Fws\u002Fchat?token=\u003Ctoken>`, send `{\"type\": \"message\", \"content\": \"...\"}`, receive `{\"type\": \"done\", \"full_response\": \"...\"}`.\n\n### System Status\n\nRun `zeroclaw status` to see provider, model, uptime, channels, memory backend. For deeper diagnostics: `zeroclaw doctor`.\n\n**REST:** `GET \u002Fapi\u002Fstatus` (same info as JSON), `GET \u002Fhealth` (no auth, quick ok\u002Fnot-ok).\n\n### Memory\n\nThe CLI can list, get, and clear memories but **cannot store** them directly. To store a memory:\n- Via agent: `zeroclaw agent -a \u003Calias> -m \"remember that my favorite color is blue\"`\n- Via REST: `POST \u002Fapi\u002Fmemory` with `{\"key\": \"...\", \"content\": \"...\", \"category\": \"core\"}`\n\n**CLI (read\u002Fdelete):**\n- `zeroclaw memory list` — list all entries\n- `zeroclaw memory list --category core --limit 10` — filtered\n- `zeroclaw memory get \"key-name\"` — get specific entry\n- `zeroclaw memory stats` — usage statistics\n- `zeroclaw memory clear --key \"prefix\" --yes` — delete entries (confirm with user first)\n\n**REST (full CRUD):**\n- `GET \u002Fapi\u002Fmemory` — list all (optional: `?query=search+text&category=core`)\n- `POST \u002Fapi\u002Fmemory` — store: `{\"key\": \"...\", \"content\": \"...\", \"category\": \"core\"}`\n- `DELETE \u002Fapi\u002Fmemory\u002F{key}` — delete entry\n\nCategories: `core`, `daily`, `conversation`, or any custom string.\n\n### Cron \u002F Scheduling\n\n**CLI:**\n- `zeroclaw cron list` — show all jobs\n- `zeroclaw cron add '0 9 * * 1-5' 'Good morning' --tz America\u002FNew_York` — recurring\n- `zeroclaw cron add-at '2026-03-11T10:00:00Z' 'Remind me'` — one-time at specific time\n- `zeroclaw cron add-every 3600000 'Check health'` — interval in ms\n- `zeroclaw cron once 30m 'Follow up'` — delay from now\n- `zeroclaw cron pause \u003Cid>` \u002F `zeroclaw cron resume \u003Cid>` \u002F `zeroclaw cron remove \u003Cid>`\n\n**REST:**\n- `GET \u002Fapi\u002Fcron` — list jobs\n- `POST \u002Fapi\u002Fcron` — add: `{\"name\": \"...\", \"schedule\": \"0 9 * * *\", \"command\": \"...\"}`\n- `DELETE \u002Fapi\u002Fcron\u002F{id}` — remove job\n\n### Tools\n\nTools are used automatically by the agent during conversations (shell, file ops, memory, browser, HTTP, web search, git, etc. — 30+ tools gated by security policy).\n\nTo see what's available: `GET \u002Fapi\u002Ftools` (REST) lists all registered tools with descriptions and parameter schemas.\n\n### Configuration\n\nEdit `~\u002F.zeroclaw\u002Fconfig.toml` directly, use `zeroclaw config set \u003Ckey>=\u003Cvalue>` for one field at a time, or delete `~\u002F.zeroclaw\u002F` and re-run `zeroclaw quickstart` for a fresh setup.\n\n**REST:**\n- `GET \u002Fapi\u002Fconfig` — get current config (secrets masked as `***MASKED***`)\n- `PUT \u002Fapi\u002Fconfig` — update config (send raw TOML as body, 1MB limit)\n\n### Providers & Models\n\n- `zeroclaw providers` — list all supported providers\n- `zeroclaw models list` — cached model catalog\n- `zeroclaw models refresh --all` — refresh from providers\n- `zeroclaw models set anthropic\u002Fclaude-sonnet-4-6` — set default model\n\nOverride per-message: `zeroclaw agent -a \u003Calias> -p anthropic --model claude-sonnet-4-6 -m \"hello\"`\n\n### Real-Time Events (SSE)\n\nREST only — useful for building dashboards or monitoring:\n```bash\ncurl -N -H \"Authorization: Bearer \u003Ctoken>\" http:\u002F\u002F127.0.0.1:42617\u002Fapi\u002Fevents\n```\nStreams JSON events: `llm_request`, `tool_call_start`, `tool_call`, `agent_start`, `agent_end`, `error`.\n\n### Cost Tracking\n\n`GET \u002Fapi\u002Fcost` — returns session\u002Fdaily\u002Fmonthly costs, token counts, per-model breakdown.\n\n### Emergency Stop\n\nConfirm with the user before running any estop command — these are disruptive.\n\n- `zeroclaw estop --level kill-all` — stop everything\n- `zeroclaw estop --level network-kill` — block all network\n- `zeroclaw estop --level tool-freeze --tool shell` — freeze specific tool\n- `zeroclaw estop status` — check current estop state\n- `zeroclaw estop resume --network` — resume\n\n### Gateway Lifecycle\n\n- `zeroclaw gateway` — start HTTP gateway (foreground)\n- `zeroclaw gateway -p 8080 --host 127.0.0.1` — custom bind\n- `zeroclaw daemon` — start gateway + channels + scheduler + heartbeat\n- `zeroclaw service install\u002Fstart\u002Fstop\u002Fstatus\u002Funinstall` — OS service management\n\n### Channels\n\nZeroClaw supports 21 messaging channels. To add one, you need to edit `~\u002F.zeroclaw\u002Fconfig.toml`. For example, to set up Telegram:\n\n```toml\n[channels]\ntelegram = true\n\n[channels_config.telegram]\nbot_token = \"your-bot-token-from-botfather\"\nallowed_users = [123456789]\n```\n\nThen restart the daemon. Check channel health with `zeroclaw channels doctor`.\n\nFor the full list of channels and their config fields, read `references\u002Fcli-reference.md` (Channels section).\n\n### Pairing (Authentication Setup)\n\nWhen `require_pairing = true` (default), REST clients need a bearer token:\n```bash\ncurl -X POST http:\u002F\u002F127.0.0.1:42617\u002Fpair -H \"X-Pairing-Code: \u003Ccode>\"\n```\nResponse includes `{\"token\": \"...\"}` — save this for subsequent requests.\n\n## Common Workflows\n\nHere are multi-step sequences you're likely to need:\n\n**\"Is my agent healthy?\"**\n1. Run `zeroclaw status` — check provider, model, channels\n2. Run `zeroclaw doctor` — check connectivity, diagnose issues\n3. If gateway needed: `curl -sf http:\u002F\u002F127.0.0.1:42617\u002Fhealth`\n\n**\"Set up a new channel\"**\n1. Read the current config: `cat ~\u002F.zeroclaw\u002Fconfig.toml`\n2. Add the channel config (edit the TOML)\n3. Restart: `zeroclaw service restart` (or restart daemon manually)\n4. Verify: `zeroclaw channels doctor`\n\n**\"Switch to a different model\"**\n1. Check available: `zeroclaw models list`\n2. Set it: `zeroclaw models set \u003Cprovider\u002Fmodel>`\n3. Verify: `zeroclaw status`\n4. Test: `zeroclaw agent -a \u003Calias> -m \"hello, what model are you?\"`\n\n## Gateway Defaults\n\n- **Port:** 42617\n- **Host:** 127.0.0.1\n- **Auth:** Pairing required (bearer token)\n- **Rate limits:** 60 webhook requests\u002Fmin, 10 pairing attempts\u002Fmin\n- **Body limit:** 64KB (1MB for config updates)\n- **Timeout:** 30 seconds\n- **Idempotency:** Optional `X-Idempotency-Key` header on `\u002Fwebhook` (300s TTL)\n- **Config location:** `~\u002F.zeroclaw\u002Fconfig.toml`\n\n## Reference Files\n\nFor the complete API specification with every endpoint, field, and edge case, read `references\u002Frest-api.md`.\n\nFor the full CLI command tree with all flags and options, read `references\u002Fcli-reference.md`.\n\nOnly load these when you need precise details beyond what's in this file — for most operations, the quick references above are sufficient.\n\n## Troubleshooting\n\n**\"zeroclaw: command not found\"** — Binary not in PATH. Check `.\u002Ftarget\u002Frelease\u002Fzeroclaw`, `~\u002F.cargo\u002Fbin\u002Fzeroclaw`, or build from source with `cargo build --release`.\n\n**\"Connection refused\" on REST calls** — Gateway isn't running. Start it with `zeroclaw gateway` or `zeroclaw daemon`.\n\n**\"Unauthorized\" (401\u002F403)** — Bearer token is missing or invalid. Re-pair via `POST \u002Fpair` with the pairing code, or check `~\u002F.zeroclaw\u002Fconfig.toml` for the stored token.\n\n**\"LLM request failed\" (500)** — Provider issue. Run `zeroclaw doctor` to check connectivity. Common causes: expired API key, provider outage, rate limiting on the provider side.\n\n**\"Too many requests\" (429)** — You're hitting ZeroClaw's rate limit. Back off — the response includes `retry_after` with the number of seconds to wait.\n\n**Agent not using tools \u002F acting limited** — Check autonomy settings in config.toml under `[autonomy]`. `level = \"read_only\"` disables most tools. Try `level = \"supervised\"` or `level = \"full\"`.\n\n**Memory not persisting** — Check `[memory]` config. If `backend = \"none\"`, nothing is stored. Switch to `\"sqlite\"` or `\"markdown\"`. Also verify `auto_save = true`.\n\n**Channel not responding** — Run `zeroclaw channels doctor` for the specific channel. Common issues: expired bot token, wrong allowed_users list, channel not enabled in `[channels]`.\n\nReport errors to the user with context appropriate to their expertise level. For beginners, explain what went wrong and suggest the fix. For experts, just show the error and the fix.\n",{"name":5,"description":7},"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fzeroclaw",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill zeroclaw",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill zeroclaw",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill zeroclaw","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fzeroclaw\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"evals\u002Fevals.json","REFERENCE","参考文档",856,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fzeroclaw\u002Fevals\u002Fevals.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcli-reference.md",9806,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fzeroclaw\u002Freferences\u002Fcli-reference.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Frest-api.md",10181,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fzeroclaw\u002Freferences\u002Frest-api.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]