auditing-claude-installation

Audit Claude Code installations for configuration conflicts, duplicates, and issues.

Updated Nov 3, 2025

Search Tags:#performance #claude code #audit #configuration #installation

Ready to run

npx skills add https://github.com/ethicalcapital/skills --skill auditing-claude-installation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auditing-claude-installation
Source: https://github.com/ethicalcapital/skills/tree/main/auditing-claude-installation
Command: npx skills add https://github.com/ethicalcapital/skills --skill auditing-claude-installation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires audit_script.py, and includes scripts (resource) components.

What problem does it solve?

Identifies configuration conflicts, duplicates, conflicting CLAUDE.md guidance, invalid hooks, MCP server issues, security risks, and performance issues within a Claude Code installation.

Core Features & Use Cases

Conflicts and Waste Audit: Checks for configuration conflicts, duplicate commands, conflicting CLAUDE.md guidance, invalid hooks, MCP server issues, security risks, and performance issues.
Problem-Specific Usage: Run when troubleshooting unexpected Claude behavior, after changes, for health checks, before project configurations, or to clean up after plugin changes.
Task Automation: Executes tasks like scanning configuration files, checking custom commands, validating CLAUDE.md files, and auditing MCP servers for performance and security.

Quick Start

Run a full audit of my Claude installation.

Frequently Asked Questions about auditing-claude-installation

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

FAQPage Schema

How do I audit Claude Code installation for configuration conflicts and performance issues?▼

You can audit Claude Code installation by running the audit_script.py script, which scans settings, commands, CLAUDE.md files, hooks, and MCP servers to detect configuration conflicts, duplicates, invalid hooks, and security risks automatically.

Why does Claude Code behave unexpectedly after plugin or configuration changes?▼

Unexpected Claude Code behavior often stems from configuration conflicts, duplicate commands, conflicting CLAUDE.md guidance, or invalid hooks introduced during plugin changes. An installation audit identifies these specific configuration conflicts and duplicates causing the unexpected behavior.

What does a Claude Code health check include for MCP servers and hooks?▼

A Claude Code health check audits MCP servers and hooks for invalid configurations, security risks, and performance problems. The audit script validates hook integrity and checks MCP server configurations to detect issues affecting installation stability.

How do I clean up duplicate commands and conflicting CLAUDE.md files?▼

To clean up duplicate commands and conflicting CLAUDE.md files, run an installation audit using audit_script.py. The script detects duplicate custom commands and conflicting guidance within CLAUDE.md files, allowing you to resolve configuration waste and conflicts.

Do I need Python to run a Claude Code installation audit?▼

Running a Claude Code installation audit requires the audit_script.py dependency. You need Python available to execute this script, which analyzes configuration files, custom commands, CLAUDE.md files, hooks, and MCP servers to generate audit results.

When should I run a Claude Code configuration audit?▼

Run a Claude Code configuration audit when troubleshooting unexpected behavior, after making configuration changes, before setting up project configurations, or to clean up following plugin modifications. The audit detects conflicts, duplicates, and performance issues across settings and MCP servers.