Claude Plugin Health Audit FAQs

Question 1

Which programming languages and tools can it detect?

Accepted Answer

It currently detects Node.js, Rust, Python, Go, Docker, Terraform, Kubernetes, and GitHub Workflows by scanning for standard configuration files like package.json, Cargo.toml, and Dockerfiles.

Question 2

Does Health Audit modify my configuration files automatically?

Accepted Answer

No, the skill defaults to a read-only report. It will only modify your .claude/settings.json file if you explicitly use the --fix flag and confirm the proposed changes.

Question 3

How does it handle global versus local plugins?

Accepted Answer

The skill intelligently checks your user-level settings (~/.claude/settings.json). If a plugin is already enabled globally, it won't suggest adding it to your project-level settings unless necessary.

Question 4

Can I preview changes before they are applied?

Accepted Answer

Yes, you can use the --dry-run flag to see exactly which plugins would be added or removed without any changes being written to disk.

Question 5

What happens if a plugin is not found in the marketplace?

Accepted Answer

If an enabled plugin is not found in the configured marketplaces, the audit will flag it as 'unknown' but will not remove it, allowing for custom or private plugins.

Claude Plugin Health Audit

Key Features

Use Cases

Claude Plugin Health Audit

Key Features

Use Cases