validate-claude-folder

Validate .claude folder configuration drift across local and CI environments.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill validate-claude-folder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-claude-folder
Source: https://github.com/jasonmichaelbell78-creator/framework/tree/main/.claude/skills/validate-claude-folder
Command: npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill validate-claude-folder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify drift and misalignment in the .claude folder by validating configuration, hooks, and references.

Core Features & Use Cases

  • Validate MCP server configuration and .mcp.json integrity.
  • Check hook references exist and skill-command alignment.
  • Detect documentation freshness and missing components to ensure release readiness.

Quick Start

Run the validator to audit your .claude folder and report any drift or missing components.

Frequently Asked Questions about validate-claude-folder

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

FAQPage Schema
How do I validate my .claude folder configuration for drift?

To validate .claude folder configuration, run an audit that checks MCP server data, hook presence, command alignment, and secret configuration to identify drift and ensure release readiness.

What is configuration drift in the .claude folder?

Configuration drift in the .claude folder occurs when hook references, MCP server data, or command alignment become misaligned, leading to missing components and reduced release readiness.

How do I check .mcp.json integrity for MCP servers?

You can check .mcp.json integrity by validating MCP server configuration against expected components, ensuring hook references exist and command alignment is maintained.

Can I use a folder validator for Claude in a CI environment?

Yes, you can validate the .claude folder in a CI environment to ensure release readiness by detecting documentation freshness, missing components, hook references, and secret configuration drift.

What's the best way to detect missing hook references in Claude configuration?

The best way to detect missing hook references is to run a validator that audits the .claude folder, checking skill-command alignment, documentation freshness, and component existence.