Neura Market Logo

OpenClaw CLI

Operate and troubleshoot the OpenClaw CLI across setup, gateway/node lifecycle, channel login, messaging, agent turns, models, plugins, and system health. Us...

Ramen

@ramensushi2026

What This Skill Does

Command-line interface for operating and troubleshooting the OpenClaw platform. Covers setup, gateway/node lifecycle, channel login, messaging, agent turns, models, plugins, and system health through a single tool.

Replaces manually checking multiple logs and dashboards by providing a unified CLI for diagnostics, status checks, and lifecycle management.

When to Use It

  • Diagnose why OpenClaw is not responding by running status, health, and doctor commands
  • Restart a gateway or node after a failure without losing profile context
  • Send a message through a specific channel and verify delivery with JSON output
  • Switch between default and isolated development profiles for testing
  • Check system health and review logs before escalating an issue

Install

$ openclaw skills install @ramensushi2026/openclaw-cli

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 <name> ... for named isolated state under ~/.openclaw-<name>.

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

Top skills in this category

Weather

@steipete

Get current weather and forecasts (no API key required).

427168k

healthcheck

@stellarhold170nt

Track water and sleep with JSON file storage

1134k

Shop

@shopify

Ultimate personal shopping assistant: find, compare, buy, gift, and reorder products across the Shop catalog containing millions of stores. Tracks orders and...

1283.0k

ClawQuest: Agent Mine - OpenClaw Managed Mining

@zhzai30

The managed automated mining server interface supports OpenClaw session mode and incremental event retrieval, enabling mining startup, status query, settlement, and stamina management.

309.3k

FlyAI — Travel, Flight & Hotel Search and Booking

@yealexchen

Search flights, hotels, attractions, concerts, and travel deals with natural language. FlyAI connects to Fliggy MCP for real-time search and booking across h...

245.2k