ooda-config

Validate and modify config.json with backups and safety checks.

5|1|Updated Mar 29, 2026

Search Tags:#automation #validation #cli #safety #config #domain-management #config.json

Ready to run

npx skills add https://github.com/mataeil/OODA-loop --skill ooda-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ooda-config
Source: https://github.com/mataeil/OODA-loop/tree/main/skills/ooda-config
Command: npx skills add https://github.com/mataeil/OODA-loop --skill ooda-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing configuration for complex projects can be error-prone and risky. ooda-config provides a safe, auditable way to view, modify, and validate config.json with automatic backups and JSON reparse to ensure integrity.

Core Features & Use Cases

View current config schema, required fields, and domain settings.
Modify values with built-in validation, backups, and re-parse checks.
Validate across safety constraints, domain rules, and lifecycle commands (rotate, lens, safety, mode, season, etc.) to prevent invalid deployments.

Quick Start

Ask /ooda-config to show your current config, then use subcommands like level, domain, safety, and validate to manage and safeguard config.json.

Frequently Asked Questions about ooda-config

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

FAQPage Schema

How do I safely manage and modify a config.json file without breaking deployments?▼

To safely manage config.json, use automated validation and backup features that inspect schema versions, required fields, and safety constraints before applying changes. This prevents invalid configurations from breaking deployments.

What is the best way to validate domain settings and safety rules in a project config?▼

Validating domain settings and safety rules involves checking schema_version, required fields, value ranges, and environment-based tokens against strict constraints. This verifies that lifecycle commands and mode settings comply with governance requirements.

How do I view current schema versions and required fields in config.json?▼

You can view current schema versions and required fields by executing specific inspection subcommands. These commands display domain settings, rotation data, lens data, and mode settings to provide a complete configuration overview.

Can I automate config.json changes while preserving backups for compliance audits?▼

Yes, you can automate config.json changes while preserving backups for compliance. The system creates automatic backups and performs JSON reparse checks to ensure data integrity and maintain an auditable modification history.

Why does my config.json validation fail when updating environment-based tokens?▼

Config.json validation fails when updating environment-based tokens if the new values violate strict safety constraints, fall outside allowed value ranges, or omit required fields defined by the current schema_version.