openclaw-config-validator
Validate, analyze, and explain OpenClaw configuration files. Use when users need to check config.json for errors, understand what a config field does, compare configs, or safely modify OpenClaw configuration. Triggers on config validation requests, schema questions, or config editing tasks.
Best use case
openclaw-config-validator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validate, analyze, and explain OpenClaw configuration files. Use when users need to check config.json for errors, understand what a config field does, compare configs, or safely modify OpenClaw configuration. Triggers on config validation requests, schema questions, or config editing tasks.
Teams using openclaw-config-validator 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/openclaw-config-validator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openclaw-config-validator Compares
| Feature / Agent | openclaw-config-validator | 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, analyze, and explain OpenClaw configuration files. Use when users need to check config.json for errors, understand what a config field does, compare configs, or safely modify OpenClaw configuration. Triggers on config validation requests, schema questions, or config editing tasks.
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
# OpenClaw Config Validator Skill para validar, analisar e explicar configurações do OpenClaw. ## Fonte da Verdade O schema oficial está em: - **Runtime** (validação): `~/.nvm/versions/node/v24.13.0/lib/node_modules/openclaw/dist/config/zod-schema*.js` - **Labels**: `dist/config/schema.js` - **Repo** (referência): https://github.com/openclaw/openclaw > **Nota**: A validação sempre usa o schema local (versão instalada) para garantir precisão. ## Scripts Disponíveis ### schema-analyzer.js ```bash node scripts/schema-analyzer.js analyze <config.json> # Analisa estrutura node scripts/schema-analyzer.js validate <config.json> # Valida schema node scripts/schema-analyzer.js labels # Lista todos os labels node scripts/schema-analyzer.js explain <field.path> # Explica um campo ``` ### config-diff.js ```bash node scripts/config-diff.js report <config.json> # Relatório completo node scripts/config-diff.js diff <config.json> # Diferenças do padrão ``` ### check-update.js ```bash node scripts/check-update.js check-update # Verifica campos novos no GitHub ``` Verifica se há campos novos no schema do repositório comparado à versão local instalada. ### auto-fix.js ```bash node scripts/auto-fix.js fix <config.json> --dry-run # Preview de correções node scripts/auto-fix.js fix <config.json> --apply # Aplica correções ``` Corrige automaticamente: - `"true"` → `true` (strings para boolean) - `"123"` → `123` (strings para number) - Enums inválidos → sugere valor correto - Detecta campos renomeados/obsoletos ### migrate.js ```bash node scripts/migrate.js migrate <config.json> --from=0.16.0 --to=0.17.0 node scripts/migrate.js migrate <config.json> --from=0.16.0 --to=0.17.0 --output=config-v17.json ``` Migra config entre versões do OpenClaw: - Detecta breaking changes - Renomeia campos automaticamente - Adiciona novos campos com valores padrão - Gera relatório de mudanças ## Validações Automáticas - Seções desconhecidas (possivelmente obsoletas) - Canais sem tipo definido - Gateway remoto sem token - Campos de segurança expostos - Valores de enum inválidos ## Como Usar **Para validar uma config:** 1. Rode `schema-analyzer.js validate` no arquivo 2. Analise erros e warnings 3. Use `auto-fix.js --dry-run` para ver correções possíveis 4. Aplique correções com `auto-fix.js --apply` 5. Re-valide **Para migrar entre versões:** 1. Use `check-update.js` para ver novos campos disponíveis 2. Use `migrate.js --from=X --to=Y --dry-run` para preview 3. Aplique com `--output` para não sobrescrever o original **Para entender um campo:** 1. Use `schema-analyzer.js explain <campo>` 2. Ou consulte os labels em schema.js **Para modificar configs com segurança:** 1. Valide a config atual primeiro 2. Faça backup 3. Use auto-fix para correções seguras 4. Aplique mudanças incrementais 5. Re-valide após cada mudança ## Referências - [Schema Reference](references/schema-reference.md) - Documentação completa - [Roadmap](ROADMAP.md) - Melhorias futuras planejadas
Related Skills
openclaw-medicine
Diagnose and fix OpenClaw gateway issues — broken configs, missing tokens, dead channels, auth failures, merge bugs, and multi-instance management. Use when openclaw is unresponsive, channels aren't starting, config is corrupted, or when managing remote openclaw instances (e.g. via SSH). Also covers migrating between config strategies (Nix-managed vs local).
openclaw-json-editing
Advanced JSON editing for OpenClaw configuration files, tools, and data structures. Handles JSON5 configs, schema validation, merge patching, env var substitution, and type-safe modifications.
openclaw-agent-run
Direct agent CLI invocations in OpenClaw. Use when running the `openclaw agent` command to trigger agent turns, targeting sessions or agents programmatically, delivering replies to channels, using --json output for automation, overriding thinking/verbose levels, or understanding session selection logic. Triggers for: "openclaw agent", "direct agent run", "send a message to agent", "--deliver", "--session-id", "agent turn", "CLI agent", "thinking level", "verbose mode", "--json output".
import-existing-ai-config
Import existing AI tool configurations (from Claude, Copilot, or Cursor) into universal-ai-config templates. Converts target-specific files into universal templates.
EchoKit Config Generator
Generate config.toml for EchoKit servers with interactive setup for ASR, TTS, LLM services, MCP servers, API key entry, and server launch
doc-ctr-validator
Validate Data Contracts (CTR) documents against Layer 8 schema standards
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
claude-config-management
Claude Code設定(リポジトリルート)の構成管理ガイド。ファイルレベルsymlinkによる設定管理、管理対象の追加・削除、Taskfileタスクの実行方法を提供する。「設定ファイルを追加して」「新しいスキルを追加して」「symlinkの状態を確認して」「Claude設定を変更して」のようにClaude Code設定の構成変更を行うときに使用する。
bigconfig-generator
Use this skill when creating or updating Bigeye monitoring configurations (bigconfig.yml files) for BigQuery tables. Works with metadata-manager skill.
ai-agent-config
Manage AI coding skills across platforms (Claude Code, Antigravity, Cursor, Windsurf) using ai-agent-config CLI. Use when the user wants to sync skills to/from GitHub, install to multiple platforms, add custom skill sources, or configure skill management settings.
agent-config-maintenance
Refactor Codex configuration files and Agent Skills by splitting concerns, deduplicating instructions, and reorganizing guidance across AGENTS.md, project docs, and skills. Use when asked to clean up AGENTS.md, move instructions into skill bundles, or standardize agent setup rules.
shellcheck-configuration
Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.