audit-config

Audits Claude plugin configuration and skill definitions for inconsistencies and redundancies.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/mesca/claude-plugins --skill audit-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-config
Source: https://github.com/mesca/claude-plugins/tree/main/plugins/wf/skills/audit-config
Command: npx skills add https://github.com/mesca/claude-plugins --skill audit-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits the .claude/ directory and this plugin to identify inconsistencies, redundancies, and deviations from Claude Code best practices.

Core Features & Use Cases

  • Verifies plugin structure and composition (presence and validity of plugin.json, hooks, and skill directories)
  • Checks settings, cross-file references, and skill definitions for proper scope, naming, and hierarchy
  • Detects redundancy, misalignments, and consistency issues across CLAUDE.md, PROJECT.md, and skills

Quick Start

Run /audit-config all to perform every check.

Frequently Asked Questions about audit-config

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

FAQPage Schema
How do I audit Claude plugin configuration for best practices?

Auditing Claude plugin configuration involves checking plugin.json, hooks, and skill directories to detect deviations from Claude Code best practices. This process validates settings integrity, naming consistency, and cross-file references to surface inconsistencies and redundancies.

What does validating .claude settings.json structure involve?

Validating .claude/settings.json structure requires checking settings integrity, scope, and hierarchy within the plugin workspace. It ensures cross-file references between CLAUDE.md, PROJECT.md, and skill definitions remain consistent and properly aligned.

How do I check skill frontmatter and naming consistency across a plugin?

Checking skill frontmatter and naming consistency involves analyzing skill definitions within plugins/wf/skills to verify proper scope, naming conventions, and hierarchy. This detects misalignments and redundancies across the plugin structure.

Can I detect cross-file reference inconsistencies in Claude Code plugins?

Yes, you can detect cross-file reference inconsistencies by auditing the .claude directory and plugin workspace. The process surfaces redundancies and misalignments across CLAUDE.md, PROJECT.md, and skill definitions to ensure plugin consistency.

What's the best way to find redundant skill definitions in a Claude plugin?

The best way to find redundant skill definitions is performing a full configuration audit across the plugin workspace. This analyzes skill frontmatter, settings, and cross-file references to surface redundancies and deviations from best practices.

When should I run a plugin structure audit on my Claude Code workspace?

You should run a plugin structure audit when you suspect inconsistencies, redundancies, or deviations from Claude Code best practices. It verifies plugin.json validity, hook presence, and skill directory composition to ensure configuration integrity.