菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/laurigates/claude-plugins --skill health-audit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| 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 |
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.
| 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 |
pwdfind . -maxdepth 2 -path '*/.claude/settings.json'find . -maxdepth 1 -name 'package.json'find . -maxdepth 1 -name 'Cargo.toml'find . -maxdepth 1 -name 'pyproject.toml'find . -maxdepth 1 -name 'requirements.txt'find . -maxdepth 1 -name 'go.mod'find . -maxdepth 1 -name 'Dockerfile'find . -maxdepth 1 \( -name 'docker-compose.yml' -o -name 'docker-compose.yaml' -o -name 'compose.yml' -o -name 'compose.yaml' \)find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml' -quit -printfind . -maxdepth 2 -name '*.tf' -quit -printfind . -maxdepth 3 \( -path '*/k8s/*' -o -path '*/kubernetes/*' \) -name '*.yaml' -quit -print| Parameter | Description |
|---|---|
--fix | Apply recommended changes to |
.claude/settings.json--dry-run | Show what would be changed without modifying files |
--verbose | Show detailed analysis of each plugin decision |
Execute this plugin relevance audit:
Analyze project files from the context above to determine the technology stack. Match indicators against the tech stack mapping in REFERENCE.md.
Run claude plugin list --json to get all available plugins from configured marketplaces. Parse the output for plugin name, description, keywords, and category.
Read .claude/settings.json and extract the enabledPlugins array. If the file does not exist or enabledPlugins is not set, treat as empty list.
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:
Print a structured report covering:
When --fix is passed:
cp .claude/settings.json .claude/settings.json.backup.claude/settings.json -- remove confirmed irrelevant plugins, add confirmed relevant plugins, preserve other settingsNote: 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.
| 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:plugins - Fix plugin registry issues/health:check - Full diagnostic scan/configure:claude-plugins - Initial plugin setup