Openclaw Config Master

Edit and validate OpenClaw Gateway config (openclaw.json / JSON5). Covers all config areas — gateway, agents, channels, models, auth, tools, commands, sessio...

Plain-language checklist for installing/evaluating this skill: - What it actually does: it helps edit/validate OpenClaw config, offers schema lookup, can run openclaw/gateway CLI commands, create backups, restore and restart the Gateway. That's consistent with the name. - Metadata mismatch: the registry lists no required binaries or config paths, but the skill clearly expects the openclaw/gateway CLI and access to your OpenClaw config (~/.openclaw/openclaw.json) and logs. Treat those as required even if not declared. - Review scripts before use: the package includes shell scripts (backup/validate/restore). Inspect their contents for any destructive or network behavior before executing them. - Protect secrets: the docs show examples referencing API keys and AppSecrets. Do not paste secrets into configs without using secure secret providers; prefer env/file-backed secret providers and check who can read those files. - Prefer manual confirmation and a test environment: avoid allowing autonomous invocation to apply changes automatically in production. If possible run this skill in a sandbox/test instance first and make a full config backup before any change. - Limit scope: restrict the skill's ability to run commands or restart services except when you explicitly approve a change. Ensure 'config.patch' flows require interactive consent. If you want, I can (1) list the shell scripts' contents and point out risky commands, or (2) produce a short procedure to safely validate and run this skill in a test environment.

Type: OpenClaw Skill Name: openclaw-config-master Version: 1.3.3 This skill bundle provides a robust set of administrative tools for managing OpenClaw Gateway configurations. It includes well-structured bash scripts for backing up, restoring, and validating the 'openclaw.json' configuration file, alongside extensive documentation covering schema definitions, migration paths, and common error patterns. The instructions in SKILL.md promote a safety-first workflow, emphasizing schema validation and official documentation checks before applying changes. No malicious patterns, data exfiltration attempts, or harmful prompt injections were identified; the skill's capabilities are entirely consistent with its stated purpose of configuration management.