config-guardian
Validate and safeguard OpenClaw config updates (openclaw.json or openclaw config set/apply). Use this skill whenever changing gateway config, models, channels, agents, tools, sessions, or routing. Enforces backup, schema validation, and safe rollback before restarts.
Best use case
config-guardian is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validate and safeguard OpenClaw config updates (openclaw.json or openclaw config set/apply). Use this skill whenever changing gateway config, models, channels, agents, tools, sessions, or routing. Enforces backup, schema validation, and safe rollback before restarts.
Teams using config-guardian should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/config-guardian/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How config-guardian Compares
| Feature / Agent | config-guardian | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validate and safeguard OpenClaw config updates (openclaw.json or openclaw config set/apply). Use this skill whenever changing gateway config, models, channels, agents, tools, sessions, or routing. Enforces backup, schema validation, and safe rollback before restarts.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Config Guardian ## Overview Use this workflow whenever editing `~/.openclaw/openclaw.json` or running `openclaw config set/apply`. It prevents invalid config, creates backups, validates against schema, and enables rollback. ## Workflow (use every time) 1. **Preflight** - Confirm the requested change and scope. - Check for sensitive keys (tokens, credentials). 2. **Backup** - Run `scripts/backup_config.sh` to create a timestamped snapshot. 3. **Validate (before change)** - Run `scripts/validate_config.sh`. - If validation fails, stop and report. 4. **Apply change** - Prefer `openclaw config set <path> <value>` for small changes. - For complex edits, edit the file directly and keep diffs minimal. 5. **Validate (after change)** - Run `scripts/validate_config.sh` again. - If it fails, restore from backup with `scripts/restore_config.sh`. 6. **Restart (only with explicit approval)** - If change requires restart, ask for approval first. - Use `openclaw gateway restart`. ## Guardrails - **Never** restart or apply config without explicit user approval. - **Never** remove keys or reorder blocks unless requested. - **Always** keep a backup before edits. - If unsure about schema: run `openclaw doctor --non-interactive` and stop on errors. ## Scripts - `scripts/backup_config.sh` — create timestamped backup - `scripts/validate_config.sh` — validate config via OpenClaw doctor - `scripts/diff_config.sh` — diff current config vs backup - `scripts/restore_config.sh` — restore backup ## Validation - Use `openclaw doctor --non-interactive` for schema validation - This checks against the actual schema that the gateway uses - Warns about unknown keys, invalid types, and security issues
Related Skills
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".
polymarket-2
Query Polymarket prediction markets - check odds, trending markets, search events, track prices.
pollinations
Pollinations.ai API for AI generation - text, images, videos, audio, and analysis. Use when user requests AI-powered generation (text completion, images, videos, audio, vision/analysis, transcription) or mentions Pollinations. Supports 25+ models (OpenAI, Claude, Gemini, Flux, Veo, etc.) with OpenAI-compatible chat endpoint and specialized generation endpoints.