Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Operate and maintain OpenClaw installations — CLI commands, config management, channel/agent/model setup, security auditing, troubleshooting, and gateway adm...
Operate and maintain OpenClaw installations — CLI commands, config management, channel/agent/model setup, security auditing, troubleshooting, and gateway adm...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Comprehensive reference for administering OpenClaw via CLI. Covers channels, agents, models, config, gateway, security, and maintenance.
Never edit openclaw.json directly. Use openclaw config set/get/unset or dedicated subcommands. Always restart gateway after config changes: openclaw gateway restart Telegram accounts: NO agent field inside account config. Route via bindings array instead. Telegram streaming: must be string "off", not boolean false. JSON values in config set need --strict-json. Verify after every change. Run openclaw status or the relevant status command.
openclaw status # overview openclaw status --deep # detailed openclaw doctor # find problems openclaw doctor --fix # auto-fix what it can openclaw gateway health # gateway health check openclaw security audit # security scan openclaw security audit --deep --fix # deep scan + auto-fix
Load the docs before turning it loose — the difference is night and day. cd ~/.openclaw claude # "Read https://docs.openclaw.ai/cli — the full CLI reference. # Now read the config and architecture pages too." # Then: "Audit this workspace for security issues."
For the full CLI cheatsheet covering all commands, config paths, and examples: → Read references/cli-cheatsheet.md
For security findings, applied fixes, and remaining remediation items: → Read references/security-audit.md
MistakeFixPut agent field in Telegram account configUse bindings array at top levelSet streaming: false (boolean)Must be streaming: "off" (string)Edited openclaw.json directlyUse CLI commands; openclaw config setForgot gateway restart after configAlways openclaw gateway restartUsed jared@ for VPS SSHMust use root@clawdbotSet dmPolicy: "open" with allowFrom: ["*"]Use "pairing" or explicit user IDsSet controlUi.allowedOrigins: ["*"]Restrict to ["http://localhost:PORT"]
Full docs: https://docs.openclaw.ai CLI: https://docs.openclaw.ai/cli Channels: https://docs.openclaw.ai/cli/channels Agents: https://docs.openclaw.ai/cli/agents Models: https://docs.openclaw.ai/cli/models Config: https://docs.openclaw.ai/cli/config
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.