health-audit

Plugin audit against detected stack (Python, Node, Rust, Go, Terraform, Docker, K8s). Use when cleaning up unused plugins or discovering stack-relevant ones for a project.

Jump to install

Repository: laurigates/claude-plugins
Last source activity: July 18, 2026 at 11:51
Detected SKILL.md language: English
Stars: 49
Forks: 7

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/laurigates/claude-plugins --skill health-audit

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

mcp-management

Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.

2026-08-08

finops-overview

FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.

2026-08-08

github-actions-finops

GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.

2026-08-08

View all from this repository

/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

Use this skill when...

Use another approach when...

Reviewing plugin relevance for current project

General health diagnostics (use /health:check)

Cleaning up unused plugins

Plugin registry corruption (use /health:plugins --fix)

Discovering relevant plugins for tech stack

Agentic optimization audit (use /health:agentic-audit)

Optimizing project-specific plugin configuration

Installing specific plugin (install directly)

Onboarding to existing project

Need comprehensive settings validation

Context

Current project: !pwd

Project settings exists: !find . -maxdepth 2 -path '*/.claude/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 . -path '*/.github/workflows/*' -maxdepth 3 -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

Parameter

Description

--fix

Apply recommended changes to

/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

Use this skill when...

Use another approach when...

Reviewing plugin relevance for current project

General health diagnostics (use /health:check)

Cleaning up unused plugins

Plugin registry corruption (use /health:plugins --fix)

Discovering relevant plugins for tech stack

Agentic optimization audit (use /health:agentic-audit)

Optimizing project-specific plugin configuration

Installing specific plugin (install directly)

Onboarding to existing project

Need comprehensive settings validation

Context

Current project: !pwd

Project settings exists: !find . -maxdepth 2 -path '*/.claude/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 . -path '*/.github/workflows/*' -maxdepth 3 -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

Parameter

Description

--fix

Apply recommended changes to

created	"2026-02-05T00:00:00.000Z"
modified	"2026-07-18T00:00:00.000Z"
compatibility	claude-code
reviewed	"2026-04-15T00:00:00.000Z"
user-invocable	false
description	Plugin audit against detected stack (Python, Node, Rust, Go, Terraform, Docker, K8s). Use when cleaning up unused plugins or discovering stack-relevant ones for a project.
allowed-tools	Bash(test ), Bash(find ), Bash(jq ), Bash(claude plugin ), Read, Write, Edit, Glob, Grep, TodoWrite, AskUserQuestion
args	[--fix] [--dry-run] [--verbose]
argument-hint	[--fix] [--dry-run] [--verbose]
name	health-audit

created	"2026-02-05T00:00:00.000Z"
modified	"2026-07-18T00:00:00.000Z"
compatibility	claude-code
reviewed	"2026-04-15T00:00:00.000Z"
user-invocable	false
description	Plugin audit against detected stack (Python, Node, Rust, Go, Terraform, Docker, K8s). Use when cleaning up unused plugins or discovering stack-relevant ones for a project.
allowed-tools	Bash(test ), Bash(find ), Bash(jq ), Bash(claude plugin ), Read, Write, Edit, Glob, Grep, TodoWrite, AskUserQuestion
args	[--fix] [--dry-run] [--verbose]
argument-hint	[--fix] [--dry-run] [--verbose]
name	health-audit

Scenario	Behavior
No `.claude/settings.json`	Create it with recommended plugins
Empty `enabledPlugins`	Suggest adding relevant plugins
Monorepo with multiple languages	Suggest all matching plugins
Plugin not in marketplace	Flag as "unknown" but don't remove
User declined changes	Respect decision, show manual instructions

Context	Command
Plugin relevance audit	`/health:audit`
Audit with auto-fix	`/health:audit --fix`
Dry-run mode	`/health:audit --dry-run`
List enabled plugins	`jq -r '.enabledPlugins[]? // empty' .claude/settings.json 2>/dev/null`
Detect project languages	`find . -maxdepth 1 \( -name 'package.json' -o -name 'Cargo.toml' -o -name 'pyproject.toml' \) -exec basename {} \;`

Flag	Description
`--fix`	Apply recommended changes (with confirmation)
`--dry-run`	Show what would be changed without modifying
`--verbose`	Show detailed reasoning for each decision

health-audit

Install options

Review the source files

/health:audit

When to Use This Skill

Context

Parameters

/health:audit

When to Use This Skill

Context

Parameters

Execution

Step 1: Detect the project technology stack

Step 2: Retrieve available plugins

Step 3: Read currently enabled plugins

Step 4: Analyze plugin relevance

Step 5: Generate the audit report

Step 6: Apply changes (if --fix)

User-Level vs Project-Level

Edge Cases

Agentic Optimizations

Flags

See Also

health-audit

Source facts

Install options

Review the source files

More from this repository

More from this repository

/health:audit

When to Use This Skill

Context

Parameters

/health:audit

When to Use This Skill

Context

Parameters

Execution

Step 1: Detect the project technology stack

Step 2: Retrieve available plugins

Step 3: Read currently enabled plugins

Step 4: Analyze plugin relevance

Step 5: Generate the audit report

Step 6: Apply changes (if --fix)

User-Level vs Project-Level

Edge Cases

Agentic Optimizations

Flags

See Also