Openclaw Config
v0.1.0Edit and validate OpenClaw Gateway config (openclaw.json / JSON5). Use when adding/changing config keys (gateway.*, agents.*, models.*, channels.*, tools.*, skills.*, plugins.*, $include) or diagnosing openclaw doctor/config validation errors, to avoid schema mismatches that prevent the Gateway from starting or weaken security policies.
⭐ 5· 3.3k·38 current·38 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the provided files and instructions. The skill focuses on locating the active config, consulting the schema, making minimal edits, validating with `openclaw doctor`, and explains $include semantics. No unrelated binaries, credentials, or config paths are required.
Instruction Scope
SKILL.md limits actions to inspecting the OpenClaw config path, fetching or referencing the schema (via the running gateway or source tree), using the `openclaw` CLI to get/set values, and running `openclaw doctor` for validation. The included script prints the resolved config path, lists the config file (ls -la) and checks permissions, then runs `openclaw doctor` if the CLI is present — all within the scope of validating/editing config.
Install Mechanism
There is no install spec (instruction-only with a small helper script). Nothing is downloaded or extracted from remote URLs, so install risk is minimal.
Credentials
The skill declares no required env vars or credentials. It only references common environment variables used to locate the config (OPENCLAW_CONFIG_PATH, OPENCLAW_STATE_DIR, CLAWDBOT_STATE_DIR), which is appropriate for a config-management utility.
Persistence & Privilege
The skill does not request permanent presence (always:false) nor modify other skills or system-wide settings. The provided script is read-only in intent (lists file and runs validation) and does not alter other skill configurations.
Assessment
This skill is coherent and limited to editing/validating OpenClaw config. Before installing: (1) review and back up your existing ~/.openclaw/openclaw.json (or OPENCLAW_CONFIG_PATH) so you can recover from mistakes; (2) be aware the included script will print the resolved config path and file metadata and will run `openclaw doctor` if that CLI is on PATH (the script does not auto-apply fixes, but `openclaw doctor --fix` would modify files — SKILL.md warns against running fixes without consent); (3) follow the skill's own advice to keep long-lived secrets out of the JSON and use env vars or credential files for API keys; (4) if you don't trust the `openclaw` CLI binary on your system, inspect or obtain it from a trusted source before using this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk970myhgwt7kqac45368dgpq6h80p6zp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
