How does it handle different settings schemas?

The skill is designed to support both 'allowedTools' and 'permissions' schema formats within the settings.json file to ensure backward compatibility.

What files does this skill specifically monitor?

It monitors agent files, skill SKILL.md files, command definitions, CAPABILITIES.md, documentation indexes, and the .claude/settings.json file.

How do I trigger the infrastructure validation check?

You can run the validation by executing 'npm run validate:claude-infra' or directly via 'npx tsx scripts/validate-claude-infra.ts'.

Is this skill suitable for automated CI/CD pipelines?

Yes. It includes a specific validation command and allows you to disable emojis via environment variables for cleaner ASCII log output in CI environments.

Why does this skill enforce a flat directory structure for agents?

Claude Code may not reliably discover or load agents located in nested subdirectories; a flat structure in .claude/agents/ ensures all agents are accessible.

Claude Infrastructure Integrity

Name: Claude Infrastructure Integrity
Author: nikhillinit

bynikhillinit

Developer Tools

Validates and maintains consistency within .claude configuration directories to ensure reliable agent behavior and CI-safe deployments.

About

The Claude Infrastructure Integrity skill serves as a dedicated linter and validator for your Claude Code environment, ensuring that agents, skills, and commands are correctly cross-referenced and structured. It automatically detects naming mismatches between files and frontmatter, validates tool permissions against settings, identifies broken documentation links, and enforces a flat directory structure for optimal agent loading. By providing a standardized validation command, it prevents runtime errors caused by orphaned capabilities or misconfigured skills, making it an essential tool for teams managing complex, multi-agent AI workflows.

Key Features

Validates cross-references between agents and their required skills
Enforces naming consistency between filenames and metadata frontmatter
Checks for broken relative links within internal project documentation
Verifies tool permissions and settings schema compliance for security
Provides a CI-ready validation script with ASCII output support
0 GitHub stars

Use Cases

Ensuring CAPABILITIES.md remains synchronized with actual available tools
Preventing broken agent configurations during collaborative development cycles
Automating infrastructure health checks within CI/CD pipelines

About

Key Features

Validates cross-references between agents and their required skills
Enforces naming consistency between filenames and metadata frontmatter
Checks for broken relative links within internal project documentation
Verifies tool permissions and settings schema compliance for security
Provides a CI-ready validation script with ASCII output support
0 GitHub stars

Use Cases

Ensuring CAPABILITIES.md remains synchronized with actual available tools
Preventing broken agent configurations during collaborative development cycles
Automating infrastructure health checks within CI/CD pipelines