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.

Ir para a instalação

Repositório: laurigates/claude-plugins
Última atividade na origem: 18 de julho de 2026 às 11:51
Idioma detectado do SKILL.md: inglês
Estrelas: 49
Forks: 7

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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

Ver todas deste repositório

/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

Opções de instalação

Revise os arquivos de origem

/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

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

/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

Mais deste repositório