Coding

OpenClaw CLI

Try it

Route OpenClaw CLI requests to the right command family and profile, then verify the outcome.

What it does

Routes OpenClaw CLI requests to the correct command family, sets runtime scope via default, --dev, or --profile contexts, and expands --help before risky actions. Prefers --json output for automation and verifies postconditions with status, health, and nodes commands. Requires explicit user confirmation before destructive operations and provides a triage sequence (status, health, doctor, gateway/node) when OpenClaw is not working.

When to use it

  • Triage 'OpenClaw not working' via status, health, and doctor
  • Pick the right command family from references/command-map.md
  • Run commands under --dev or a named --profile state
  • Verify outcomes with --json output and postcondition checks

The skill document

OpenClaw CLI

Run OpenClaw commands safely and efficiently. Choose the right command family, execute with the correct profile context, and verify postconditions.

Execution Workflow

  1. Clarify the target state. Ask what should change and what must remain untouched.

  2. Select runtime scope first. Use default profile unless isolation is requested. Use:

  • openclaw --dev ... for isolated dev state under ~/.openclaw-dev.
  • openclaw --profile ... for named isolated state under ~/.openclaw-.

  1. Choose the command family. Use references/command-map.md to route the request quickly.

  2. Expand command details before running risky operations. Run openclaw --help for starred families and confirm flags.

  3. Prefer machine-readable output when automation is needed. Use --json where available, then parse/verify.

  4. Verify outcomes explicitly. Check with openclaw status, openclaw health, openclaw nodes status --json, or command-specific follow-up.

Safety Rules

  • 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.

Triage Sequence

For generic "OpenClaw not working" issues:

  1. Run openclaw status.
  2. Run openclaw health.
  3. Run openclaw doctor.
  4. Check openclaw gateway ..., openclaw node ..., or openclaw nodes ... based on where failure appears.
  5. Escalate to targeted commands in references/command-map.md.

Resources

  • references/command-map.md: Command families, routing guidance, and practical recipes.

Questions people ask

How does the skill decide which OpenClaw command to run?
It uses references/command-map.md to route the request, then expands --help for starred command families before executing risky actions.
Does the skill run destructive commands automatically?
No. It requires explicit user confirmation before reset, uninstall, force-based flows, or credential-clearing operations.
Which commands does it use to verify results?
openclaw status, openclaw health, openclaw nodes status --json, plus command-specific follow-up checks.

Related skills

Memory

Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.

by Iván559 installs18 stars

diagram-generator

Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.

by nssa.io1.0k installs47 stars

Join meeting

Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.

by johnpatternai22 installs8 stars

Productivity

Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.

by Iván855 installs69 stars

AdMapix

Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.

by fly0pants4.3k installs296 stars