Terminal
Terminal/Skill
Guides an AI agent through administering a GoClaw gateway with its CLI: health checks, agents, skills, traces, and troubleshooting, with confirmation before changes.
By Next Level Builder
Works with
npx skills add nextlevelbuilder/goclaw --skill goclawUse this skill when the user asks you to operate, inspect, administer, or debug a
GoClaw gateway through the goclaw CLI/runtime package.
.env contents in chat, issues,
comments, or logs.--help output.Do not run bare goclaw unless the user explicitly wants to start the gateway
server. Use goclaw --help, goclaw version, or a subcommand for inspection.
Start with read-only discovery:
command -v goclaw
type -a goclaw
goclaw version
goclaw --help
goclaw <command> --help
If command -v goclaw is empty on a managed server, also check deployment
runtime paths before concluding the CLI is absent:
ls -l /var/lib/goclaw/data/.runtime/bin/goclaw
ls -l /app/data/.runtime/bin/goclaw
Distinguish the command surface you found:
goclaw with no subcommand starts the gateway.agent, skills, traces,
sessions, providers, channels, cron, config, doctor, auth,
backup, restore, migrate, and upgrade.GOCLAW_SERVER,
GOCLAW_GATEWAY_URL, and GOCLAW_GATEWAY_TOKEN from the environment.
Configure tokens through the shell/session secret manager, not CLI argv or
pasted text.Use placeholders in examples:
goclaw traces list
Run safe checks first:
goclaw doctor
goclaw config path
goclaw config validate
goclaw agent list
goclaw skills list
goclaw sessions list
goclaw providers list
goclaw channels list
goclaw cron list
goclaw traces list
If a command requires a running gateway, retry with the correct remote target:
goclaw agent list
Use goclaw config show only in a private local terminal when necessary. Treat
the output as sensitive even though the CLI redacts known secret fields; do not
paste it into chats, issues, PRs, or shared logs.
For HTTP-only surfaces, inspect the current API/docs before guessing endpoint
shape. Useful areas include /health, /v1/skills, /v1/traces,
/v1/packages/runtimes, /v1/mcp, and /v1/providers when available.
Read first:
goclaw agent --help
goclaw agent list
Before create, update, chat, or delete operations, verify target tenant/org and
agent ID/key. Treat agent delete as destructive.
Read first:
goclaw skills --help
goclaw skills list
goclaw skills show <skill>
goclaw skills deps status <skill-id-or-path>
goclaw skills access get <skill-id>
Use dependency scan/check before install:
goclaw skills deps scan <skill-id-or-path>
goclaw skills deps check <skill-id-or-path>
Mutating skill commands need clear intent and scope:
goclaw skills deps install <skill-id>
goclaw skills access set <skill-id> --help
goclaw skills grant agent <skill-id> <agent-id>
goclaw skills revoke agent <skill-id> <agent-id>
System skills are bundled and should not be edited in place. Prefer uploading or publishing a tenant/custom skill override when customization is required.
First inspect whether this CLI version exposes MCP commands:
goclaw mcp --help
If no MCP CLI exists, use the current gateway API/UI/docs for MCP discovery and permission changes. Do not invent command names. For tool access issues, verify:
Inspect current runtime/package support before acting:
goclaw packages --help
goclaw skills deps status <skill-id-or-path>
If there is no packages CLI, use the Packages UI or /v1/packages/* API when
available. Install/update/remove package operations are admin-level and may need
approval. Prefer the smallest dependency needed by the selected skill.
Use read-only status commands first:
goclaw auth status
goclaw auth status <provider>
For gateway bearer tokens, provider keys, OAuth refresh tokens, and CLI credentials:
Use traces to debug provider errors, tool failures, channel delivery, and stuck sessions:
goclaw traces --help
goclaw traces list --status error
goclaw traces get <trace-id> -o json
goclaw traces timeline <trace-id>
goclaw traces follow --session <session-key>
goclaw traces export <trace-id>
Redact prompts, tokens, URLs with secrets, headers, and customer data before posting trace excerpts anywhere public.
Inspect help and list commands:
goclaw sessions --help
goclaw channels --help
goclaw providers --help
goclaw cron --help
Treat these as sensitive:
sessions delete and sessions reset;goclaw auth status or the relevant credential status command.goclaw providers list and provider verification help.goclaw skills list and goclaw skills show <skill>.goclaw channels list and the failed trace.Ask for confirmation before running commands that:
Confirmation should include the target, command category, expected effect, and rollback path if one exists.