Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Operate and troubleshoot the OpenClaw CLI across setup, gateway/node lifecycle, channel login, messaging, agent turns, models, plugins, and system health. Us...
Operate and troubleshoot the OpenClaw CLI across setup, gateway/node lifecycle, channel login, messaging, agent turns, models, plugins, and system health. Us...
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Run OpenClaw commands safely and efficiently. Choose the right command family, execute with the correct profile context, and verify postconditions.
Clarify the target state. Ask what should change and what must remain untouched. Select runtime scope first. Use default profile unless isolation is requested. Use: openclaw --dev ... for isolated dev state under ~/.openclaw-dev. openclaw --profile <name> ... for named isolated state under ~/.openclaw-<name>. Choose the command family. Use references/command-map.md to route the request quickly. Expand command details before running risky operations. Run openclaw <command> --help for starred families and confirm flags. Prefer machine-readable output when automation is needed. Use --json where available, then parse/verify. Verify outcomes explicitly. Check with openclaw status, openclaw health, openclaw nodes status --json, or command-specific follow-up.
Require explicit user confirmation before reset, uninstall, destructive --force flows, or credential-clearing operations. Prefer non-destructive diagnostics first: status, health, doctor, logs. Keep profile usage consistent across a workflow. Do not mix default and --dev/--profile commands accidentally. For gateway issues, diagnose before restart unless restart is explicitly requested.
For generic "OpenClaw not working" issues: Run openclaw status. Run openclaw health. Run openclaw doctor. Check openclaw gateway ..., openclaw node ..., or openclaw nodes ... based on where failure appears. Escalate to targeted commands in references/command-map.md.
references/command-map.md: Command families, routing guidance, and practical recipes.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.