Health Audit

/health:audit

Audit the project's enabled plugins against the actual technology stack. Identifies plugins that don't apply to this project and suggests relevant plugins that aren't enabled.

When to Use This Skill

Context

• Current project: !pwd
• Project settings exists: !find .claude -maxdepth 1 -name 'settings.json'
• Package.json exists: !find . -maxdepth 1 -name 'package.json'
• Cargo.toml exists: !find . -maxdepth 1 -name 'Cargo.toml'
• pyproject.toml exists: !find . -maxdepth 1 -name 'pyproject.toml'
• requirements.txt exists: !find . -maxdepth 1 -name 'requirements.txt'
• go.mod exists: !find . -maxdepth 1 -name 'go.mod'
• Dockerfile exists: !find . -maxdepth 1 -name 'Dockerfile'
• docker-compose exists: !find . -maxdepth 1 \( -name 'docker-compose.yml' -o -name 'docker-compose.yaml' -o -name 'compose.yml' -o -name 'compose.yaml' \)
• GitHub workflows: !find .github/workflows -maxdepth 1 -name '*.yml' -quit -print
• Terraform files: !find . -maxdepth 2 -name '*.tf' -quit -print
• Kubernetes manifests: !find . -maxdepth 3 \( -path '*/k8s/*' -o -path '*/kubernetes/*' \) -name '*.yaml' -quit -print

Parameters

Execution

Execute this plugin relevance audit:

Step 1: Detect the project technology stack

Analyze project files from the context above to determine the technology stack. Match indicators against the tech stack mapping in REFERENCE.md.

Step 2: Retrieve available plugins

Run claude plugin list --json to get all available plugins from configured marketplaces. Parse the output for plugin name, description, keywords, and category.

Step 3: Read currently enabled plugins

Read .claude/settings.json and extract the enabledPlugins array. If the file does not exist or enabledPlugins is not set, treat as empty list.

Step 4: Analyze plugin relevance

Compare each enabled plugin against the detected tech stack. Use the plugin relevance mapping in REFERENCE.md to determine which plugins are relevant, irrelevant, or missing.

Categorize each plugin as:

• RELEVANT -- matches detected tech stack
• NOT RELEVANT -- no matching indicators found
• MISSING -- relevant plugin not currently enabled

Step 5: Generate the audit report

Print a structured report covering: 1. Detected technology stack with evidence 2. Currently enabled plugins with relevance status 3. Suggested plugins to add (with reasons) 4. Suggested plugins to remove (with reasons) 5. Summary counts

Step 6: Apply changes (if --fix)

When --fix is passed:

1. Back up current settings: cp .claude/settings.json .claude/settings.json.backup 2. Ask for confirmation before each category of changes (removals, additions) 3. Update .claude/settings.json -- remove confirmed irrelevant plugins, add confirmed relevant plugins, preserve other settings 4. Verify changes by re-reading the file, confirming valid JSON, and showing the diff

User-Level vs Project-Level

Note: This command only manages project-level plugin settings in .claude/settings.json.

User-level plugins (in ~/.claude/settings.json) are managed separately and don't need duplication at project level.

When analyzing, check if a plugin is already enabled at user level:

jq -r '.enabledPlugins[]? // empty' ~/.claude/settings.json 2>/dev/null

If a plugin is enabled at user level, it doesn't need to be in project settings unless you want project-specific behavior.

Edge Cases

Agentic Optimizations

Flags

See Also

• /health:plugins - Fix plugin registry issues
• /health:check - Full diagnostic scan
• /configure:claude-plugins - Initial plugin setup

Health Audit Reference

Tech Stack Detection Mapping

Plugin Relevance Mapping

Report Template

Plugin Audit Report
===================
Project: <current-directory>
Date: <timestamp>

Detected Technology Stack
-------------------------
- TypeScript/JavaScript (package.json, tsconfig.json)
- Docker (Dockerfile, docker-compose.yml)
- GitHub Actions (.github/workflows/)

Currently Enabled Plugins (N)
-----------------------------
+ typescript-plugin     - RELEVANT (TypeScript project)
+ git-plugin            - RELEVANT (all repos)
x kubernetes-plugin     - NOT RELEVANT (no K8s manifests found)
x terraform-plugin      - NOT RELEVANT (no .tf files found)
x python-plugin         - NOT RELEVANT (no Python indicators)

Suggested Plugins to Add (N)
----------------------------
+ container-plugin      - Docker files detected
+ github-actions-plugin - Workflow files detected
+ testing-plugin        - Test configuration detected

Suggested Plugins to Remove (N)
-------------------------------
- kubernetes-plugin     - No K8s usage detected
- terraform-plugin      - No Terraform usage detected
- python-plugin         - No Python usage detected

Summary
-------
Enabled: N plugins
Relevant: N plugins
Irrelevant: N plugins (consider removing)
Missing: N plugins (consider adding)

Run `/health:audit --fix` to apply these recommendations.