nextclaw-self-manage

name	nextclaw-self-manage
description	Self-manage NextClaw runtime via CLI guide. For install/start/status/doctor/service/channels/config/agents/cron/remote/update operations, and for discovering local HTTP/API/webhook addresses.
description_zh	通过 NextClaw CLI 管理 NextClaw 自身，覆盖安装、启动、状态、诊断、服务、渠道、配置、Agent、定时任务、远程访问、更新，以及本地 HTTP/API/webhook 地址发现。
metadata	{"nextclaw":{"always":true,"emoji":"🛠️"}}

NextClaw Self-Management

Use this skill whenever the user asks to manage NextClaw itself (version, service status, diagnostics, channels, config, agents, cron, remote, update, installed skills, marketplace skills, local HTTP/API/webhook addresses).

Source of Truth

Always use the built-in NextClaw self-management guide as the operation guide.

1. Read the built-in guide path provided by the system prompt first.
2. If the packaged guide is unavailable in a repo source checkout, use repo docs path docs/USAGE.md.
3. Never treat workspace USAGE.md snapshots or copied artifacts as the source of truth.
4. If both guide paths are unavailable, use nextclaw --help and nextclaw <subcommand> --help as fallback and tell the user that guide file is missing.

Routing Rules

• Treat NextClaw self-management as a product-management intent, not a generic "create/install/publish" intent.
• Read the built-in self-management guide before opening unrelated generic skills.
• Example: "create a new Agent" maps to NextClaw agent management, not skill-creator.

Stable Execution Rules

• Map version lookup directly to nextclaw --version; do not substitute status for version queries.
• Prefer machine-readable output: use --json when available.
• Before calling local HTTP APIs or /webhook, run nextclaw status --json and read endpoints.uiUrl / endpoints.apiUrl; do not guess the service port.
• For webhook payload details, read the focused guide linked from the self-management guide only when you need to implement or debug a webhook caller.
• Execute only commands documented in the self-management guide or CLI help; do not invent commands or config paths.
• In desktop-installed runtimes, still use the same nextclaw ... commands. The desktop launcher provides a managed command surface to AI command tools; do not ask the user to install the NPM CLI just to run self-management commands.
• Keep installed skills and marketplace catalog as two different domains:
  • local installed: nextclaw skills installed|info
  • marketplace catalog and installed marketplace lifecycle: nextclaw marketplace skills search|info|recommend|install|update
• After mutating operations, close the loop with:
  • nextclaw status --json
  • and nextclaw doctor --json when needed
• Be explicit about restart semantics after changes.
• After modifying a running Service App, run nextclaw app restart <app-id> --json before validating through the live product UI or panel-to-service action calls.
• For channel discovery before messaging, use nextclaw channels list --json and treat returned channels[].id values as authoritative.
• For cron notifications, do not add delivery flags to the cron command. Put the notification intent in the scheduled message and let the scheduled agent call the message tool with an explicit channel and recipient.
• For Agent creation/update/removal, treat nextclaw agents list|new|update|remove --json as the default path and follow the Agent management section in the self-management guide.
• Do not edit config.json or agents.list directly for normal Agent CRUD; only do that when the user explicitly wants a manual recovery path.
• When creating an Agent, prefer an explicit non-text avatar and avoid text-based styles such as DiceBear initials.

Minimal Self-Management Flow

1. Understand user intent and map to one concrete CLI action.
2. Read the relevant section in the self-management guide.
3. Execute the documented command with safe parameters.
4. Verify with status/doctor.
5. Report outcome + next action (if any).

Release Notes / Changelog Lookup

When user asks "what changed in version X", follow:

• references/release-notes-changelog.md
• Do not claim details without a traceable source path.

High-frequency Intents

• Version lookup: nextclaw --version
• Service health: nextclaw status --json / nextclaw doctor --json
• Local HTTP/API/webhook addresses: nextclaw status --json and read endpoints.uiUrl / endpoints.apiUrl
• Lifecycle: nextclaw start|restart|stop
• Service App live runtime: nextclaw app restart <app-id> --json
• Channels: nextclaw channels list --json|status|login
• Config: nextclaw config get|set|unset
• Agents: nextclaw agents list|new|update|remove
• Automation: nextclaw cron list|add|remove|enable|run
• Installed skills: nextclaw skills installed|info
• Marketplace skills: nextclaw marketplace skills search|info|recommend|install|update