ClawHub

OpenClaw CLI

v1.0.0

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

⭐ 6· 7.1k·79 current·83 all-time
byRamen@ramensushi2026

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for ramensushi2026/openclaw-cli.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "OpenClaw CLI" (ramensushi2026/openclaw-cli) from ClawHub.
Skill page: https://clawhub.ai/ramensushi2026/openclaw-cli
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install openclaw-cli

ClawHub CLI

Package manager switcher

npx clawhub@latest install openclaw-cli
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the content: the skill routes requests to OpenClaw CLI command families, explains profiles (~/.openclaw-*) and triage flows. It does not request unrelated credentials or binaries.
✓
Instruction Scope
SKILL.md instructs the agent to choose commands, run 'openclaw' subcommands, prefer --json for automation, and verify outcomes. It references local profile paths and diagnostic commands but does not instruct reading unrelated files or exfiltrating data. It explicitly requires confirmation before destructive flows.
✓
Install Mechanism
No install spec or remote downloads are included — this is instruction-only, so nothing is written to disk by the skill itself.
✓
Credentials
The skill declares no environment variables or credentials. It sensibly references local OpenClaw profile directories and CLI operations that may themselves require tokens when the CLI runs; requesting no secrets in the skill metadata is proportionate.
✓
Persistence & Privilege
always is false and the skill does not request persistent or elevated platform privileges. It does not modify other skills or system-wide settings in its instructions.
Assessment
This skill is a guidance layer for running your local 'openclaw' CLI — it does not bundle code or request credentials. Before using it, ensure you trust the installed openclaw binary and have backups of any important local config. Allow the agent to execute commands only when you approve them, and be especially cautious when running destructive commands (reset, uninstall, --force) even though the skill instructs the agent to ask for confirmation.

Like a lobster shell, security has layers — review code before you run it.

latestvk97fshg8axgeqdme6khyzae53181h35t
7.1kdownloads
6stars
1versions
Updated 2mo ago
v1.0.0
MIT-0
Ramen@ramensushi2026
latest
Download

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.

Comments

Loading comments...