qclaw-openclaw

Execute OpenClaw CLI commands via platform-aware wrappers with environment injection.

1|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/bluegitter/QClaw --skill qclaw-openclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qclaw-openclaw
Source: https://github.com/bluegitter/QClaw/tree/main/resources/openclaw/config/skills/qclaw-openclaw
Command: npx skills add https://github.com/bluegitter/QClaw --skill qclaw-openclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, node, and includes scripts (resource) components.

What problem does it solve?

QClaw environments do not provide a global openclaw CLI, so direct invocation of openclaw commands fails or runs with incorrect runtime context. This Skill centralizes execution through platform-aware wrapper scripts that inject required environment variables, state and config paths, and prevent unsafe service lifecycle operations managed by the QClaw Electron supervisor.

Core Features & Use Cases

  • Platform-aware wrappers for macOS and Windows that read runtime metadata from ~/.qclaw/qclaw.json and execute openclaw.mjs via the embedded Node binary.
  • Safe configuration workflow that enforces schema validation, requires official documentation confirmation before writes, and implements transactional backup-and-rollback for any config modifications.
  • Command scoping & policy that allows read-only queries (status/health/gateway status), configuration management, cron/model/skills/plugins management, diagnostics, logs, and memory/session operations while forbidding any gateway/daemon start/stop/install/uninstall or other destructive lifecycle commands.
  • Operational diagnostics to collect health, doctor, and log information without performing service restarts or manipulations.

Quick Start

Invoke the macOS wrapper script in this skill's scripts directory to run a safe OpenClaw CLI read or write, for example: bash <skill_dir>/scripts/openclaw-mac.sh config get gateway.port

Frequently Asked Questions about qclaw-openclaw

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run openclaw commands without a global CLI installed?

To run openclaw commands without a global CLI, use a wrapper script that executes openclaw.mjs via an embedded Node binary. This injects required environment variables and state paths from your local configuration.

How do I safely modify openclaw configuration files?

Safely modify openclaw configuration by enforcing schema validation and requiring official documentation confirmation before writes. The system creates transactional backups, enabling rollback if the configuration changes cause issues.

Can I use the openclaw CLI to start and stop the gateway daemon?

You cannot use the openclaw CLI wrapper to start, stop, install, or uninstall the gateway daemon. The wrapper explicitly forbids these destructive service lifecycle operations to prevent supervisor conflicts.

Does the openclaw wrapper support both macOS and Windows environments?

The openclaw wrapper supports both macOS and Windows environments through platform-aware scripts. These scripts read runtime metadata from the local configuration file to execute commands correctly.

What openclaw commands are allowed for cron job scheduling and diagnostics?

Allowed openclaw commands for cron job scheduling and diagnostics include read-only status queries, configuration management, model and skills management, and health checks. Service restarts and manipulations are blocked.

Why does direct openclaw CLI invocation fail in the QClaw environment?

Direct openclaw CLI invocation fails in QClaw environments because it lacks a global binary and runs with incorrect runtime context. The wrapper centralizes execution through the QClaw-managed runtime to resolve this.