validate-schemas

Validate agent configuration files against the latest schema.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/chetmancini/agent-smith --skill validate-schemas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-schemas
Source: https://github.com/chetmancini/agent-smith/tree/main/skills/validate-schemas
Command: npx skills add https://github.com/chetmancini/agent-smith --skill validate-schemas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates the installed agent config against the latest schema, surfaces new features to adopt, and flags deprecated config for removal. Use when asked to validate settings, check schema, update schemas, verify configuration files, or review config for new/deprecated options.

Core Features & Use Cases

  • Refreshes the active agent's schema cache
  • Validates the installed configuration files against the schema
  • Discovers and surfaces new features for adoption
  • Flags deprecated options for removal or migration
  • Use Case: Run validation after changing settings or onboarding a new agent to ensure config coherence.

Quick Start

Run the validate-schemas command to refresh the active agent's schema cache and validate your installed configuration files.

Frequently Asked Questions about validate-schemas

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

FAQPage Schema
How do I validate agent config against the latest schema?

To validate agent config, run the validate-schemas command to refresh the active schema cache and verify installed configuration files against the latest specifications.

Does schema validation work with Claude Code and OpenCode?

Yes, schema validation applies to Claude Code, Codex, Grok, OpenCode, Pi, and related toolchains, checking configurations for new, unknown, or deprecated settings across these platforms.

Why should I check agent config for deprecated settings?

Checking for deprecated settings ensures config coherence by flagging outdated options for removal or migration, while simultaneously discovering new features available in the refreshed schema cache.

When do I need to run schema validation on my configuration files?

Run schema validation after changing settings or onboarding a new agent to ensure config coherence, verify configuration files, and review config for new or deprecated options.

What is the best way to discover new features in my agent config?

The best way to discover new features is running schema validation, which refreshes the local schema cache and surfaces newly available settings for adoption across your active agent toolchain.

Can I detect config drift across multiple AI agent toolchains?

Yes, you can detect config drift by validating installed configuration files against the latest schema, which reports unknown or deprecated settings across Claude Code, Codex, Grok, OpenCode, and Pi.