config-validator

Validate docker-compose, LiteLLM, and agent identity configuration files.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Heretek-AI/heretek-openclaw --skill config-validator-heretek-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-validator
Source: https://github.com/Heretek-AI/heretek-openclaw/tree/main/skills/config-validator
Command: npx skills add https://github.com/Heretek-AI/heretek-openclaw --skill config-validator-heretek-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Config Validator identifies misconfigurations across docker-compose, LiteLLM, and agent identities, preventing deployment failures and downtime.

Core Features & Use Cases

  • Validates docker-compose.yml for all 11 agents
  • Checks litellm_config.yaml endpoints and model references
  • Verifies presence of agent identity files
  • Ensures unique port assignments and complete environment variables
  • Reports results in structured JSON

Quick Start

Run the validation script to generate a real-time report of deployment configuration health.

Frequently Asked Questions about config-validator

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

FAQPage Schema
How do I validate docker-compose configuration for multiple agents?

Validate docker-compose configuration by running a script that checks for all 11 required agents, ensuring unique port assignments and complete environment variables to prevent deployment failures.

What does LiteLLM configuration validation check for?

LiteLLM configuration validation checks endpoints and model references in litellm_config.yaml, verifying coherence across deployment artifacts to prevent runtime failures and downtime.

Can I check if agent identity files are present before deploying?

Yes, configuration validation verifies the presence of agent identity files alongside docker-compose and LiteLLM configs, producing a structured JSON report of deployment health.

How do I ensure port uniqueness across multi-service deployments?

Ensure port uniqueness by applying validation checks to deployment artifacts, which detect duplicate port assignments in docker-compose configurations before runtime failures occur.

What is the best way to prevent deployment misconfigurations in OpenClaw?

Prevent deployment misconfigurations by validating configuration correctness across docker-compose, LiteLLM, and agent identity files, implementing checks for required files, port uniqueness, and JSON schema validity.

Does configuration validation report results in a structured format?

Yes, configuration validation produces a structured JSON report detailing the completeness and coherence of deployment artifacts after running real-time health checks.