Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
laurigates avatar

Health Check

  • 64 installs
  • 49 repo stars
  • Updated August 4, 2026
  • laurigates/claude-plugins

Helps with ai & agent building tasks.

About

health-check is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • health-check
  • AI & Agent Building
  • AI-coding skill

Health Check by the numbers

  • 64 all-time installs (skills.sh)
  • Ranked #6,160 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/laurigates/claude-plugins --skill health-check

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs64
repo stars49
Last updatedAugust 4, 2026
Repositorylaurigates/claude-plugins

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

/health:check

Single entry point for Claude Code health diagnostics. Runs environment checks (plugin registry, settings, hooks, MCP servers, SessionStart executability, pre-commit validity, permissions coverage, marketplace enrollment) plus optional deeper audits, and routes --fix to the appropriate internal workflow.

When to Use This Skill

Use this skill when...Use another approach when...
Running Claude Code diagnosticsViewing raw settings (use Read on settings.json)
Troubleshooting plugin registry issuesInspecting marketplace metadata manually
Auditing plugins for project fitInstalling a specific plugin (use /plugin install)
Checking skill agentic-optimisation qualityEditing a single known skill
One-stop --fix across registry/stack/agenticPrecise surgical edits to a single file

Context

  • Current project: !pwd
  • Project settings exists: !find .claude -maxdepth 1 -name 'settings.json'
  • Local settings exists: !find .claude -maxdepth 1 -name 'settings.local.json'

Parameters

Parse these from $ARGUMENTS:

ParameterDescription
`--scope=<all\registry\
--fixApply fixes to findings (prompts for confirmation).
--dry-runPreview fixes without modifying files.
--verboseInclude detailed diagnostics.

Scope semantics:

ScopeCovers
registryPlugin registry health (orphaned projectPath, stale enabledPlugins, registry-vs-settings drift)
stackEnabled plugins vs detected project tech stack
agenticSkill/command/agent agentic-optimisation compliance
runtime~/.claude.json bloat (dead projects[], dead githubRepoPaths[*], orphaned disabledMcpServers, duplicate MCP naming). Read-only audit.
allEnvironment checks + all four audits

Execution

Execute this diagnostic router. Default scope is all when --scope is not provided.

Step 1: Run environment checks (always)

Environment checks run regardless of --scope. They cover the baseline health of the Claude Code installation and the current project's .claude/ directory.

1a. Core environment scripts
bash "${CLAUDE_SKILL_DIR}/scripts/check-plugins.sh" --home-dir "$HOME" --project-dir "$(pwd)"
bash "${CLAUDE_SKILL_DIR}/scripts/check-settings.sh" --home-dir "$HOME" --project-dir "$(pwd)"
bash "${CLAUDE_SKILL_DIR}/scripts/check-hooks.sh" --home-dir "$HOME" --project-dir "$(pwd)"
bash "${CLAUDE_SKILL_DIR}/scripts/check-mcp.sh" --home-dir "$HOME" --project-dir "$(pwd)"

Parse STATUS= and ISSUES: from each. Pass --verbose when set on $ARGUMENTS.

1b. SessionStart smoke test

Check whether scripts/install_pkgs.sh (or any script registered in the SessionStart hook in .claude/settings.json) is executable and exits cleanly in both remote and local contexts.

1. Locate the SessionStart hook command from .claude/settings.json (look for the command field). 2. If a script is found, run:

   CLAUDE_CODE_REMOTE=true bash <script-path>

Capture exit code. Expected: 0. 3. Run again to verify idempotency — expected: 0. 4. Run with remote guard off:

   CLAUDE_CODE_REMOTE=false bash <script-path>

Expected: 0 (typically a no-op). 5. Report:

  • OK: All three exit 0
  • WARN: Script exists but is not registered in settings.json hook
  • ERROR: Script exits non-zero, or script referenced in hook does not exist
1c. Pre-commit config validator

If .pre-commit-config.yaml exists:

pre-commit validate-config .pre-commit-config.yaml

Report:

  • OK: exits 0 (config is valid)
  • WARN: pre-commit not installed — skip check, suggest pip install pre-commit
  • ERROR: exits non-zero — show validation error
1d. Permissions coverage check

Compare tools referenced in project files against permissions.allow in .claude/settings.json.

1. Read permissions.allow from .claude/settings.json. Extract the command prefix from each Bash(<prefix>:*) entry. 2. Scan these files for tool invocations:

  • justfile / Justfile — commands on recipe lines
  • Makefile — shell commands on recipe lines
  • .pre-commit-config.yamlentry: fields

3. For each tool found in project files:

  • Flag as MISSING if no matching Bash(<tool>:*) entry exists in permissions.allow

4. For each Bash(<tool>:*) entry in permissions.allow:

  • Flag as UNUSED if the tool is not found in any project file (informational, not an error)

Scoring:

  • OK: No missing permissions
  • WARN: 1–3 missing permissions
  • ERROR: 4+ missing permissions
1e. Marketplace enrollment check

The local marketplace key (set by claude marketplace add <name>) is user-chosen and varies between installs (commonly laurigates-claude-plugins, sometimes claude-plugins). Identify the marketplace by its stable source.repo, not by a hardcoded local key.

1. Read .claude/settings.json. 2. Scan all entries under extraKnownMarketplaces and find the one whose source.repo equals "laurigates/claude-plugins". Capture that entry's key as $MP_KEY. 3. Check that enabledPlugins contains at least one key with the suffix @$MP_KEY. 4. Report:

  • OK: Both checks pass
  • WARN: enabledPlugins has no @$MP_KEY entries (marketplace enrolled but no plugins enabled)
  • ERROR: no extraKnownMarketplaces entry with source.repo = laurigates/claude-plugins (run /configure:claude-plugins --fix to add it)

Reference jq snippet (for verification or fix scripts):

MP_KEY=$(jq -r '.extraKnownMarketplaces // {} | to_entries | map(select(.value.source.repo == "laurigates/claude-plugins")) | .[0].key // empty' .claude/settings.json)
if [ -z "$MP_KEY" ]; then
  echo "ERROR: no extraKnownMarketplaces entry with source.repo = laurigates/claude-plugins"
else
  jq -e --arg k "@$MP_KEY" '.enabledPlugins // {} | to_entries | map(select(.key | endswith($k))) | length > 0' .claude/settings.json >/dev/null \
    && echo "OK: marketplace enrolled as $MP_KEY with enabled plugins" \
    || echo "WARN: marketplace $MP_KEY enrolled but no @${MP_KEY} entries in enabledPlugins"
fi

Step 2: Run scope-specific audits

For --scope=registry or all:

bash "${CLAUDE_PLUGIN_ROOT}/skills/health-plugins/scripts/check-registry.sh" \
  --home-dir "$HOME" --project-dir "$(pwd)"

Parse STATUS=, PLUGIN_COUNT=, ORPHANED_ENTRIES=, STALE_ENABLED_ENTRIES=, and ISSUES:.

For --scope=stack or all: follow the tech-stack audit steps from the internal health-audit skill (see ${CLAUDE_PLUGIN_ROOT}/skills/health-audit/SKILL.md and its REFERENCE.md).

For --scope=agentic or all: follow the skill-quality audit steps from the internal health-agentic-audit skill (see ${CLAUDE_PLUGIN_ROOT}/skills/health-agentic-audit/SKILL.md and its REFERENCE.md).

For --scope=runtime or all:

bash "${CLAUDE_SKILL_DIR}/scripts/check-runtime.sh" --home-dir "$HOME" --project-dir "$(pwd)"

Parse STATUS=, RUNTIME_SIZE_BYTES=, PROJECTS_TOTAL=, PROJECTS_DEAD=, GH_PATHS_TOTAL=, GH_PATHS_DEAD=, ORPHAN_DISABLED_MCP=, DUPLICATE_MCP=, CLEANUP_SUGGESTED=, and ISSUES:. Pass --verbose to list every dead path / orphaned server (default is a single rolled-up issue per category to keep output compact).

The runtime scope audits ~/.claude.json — the harness state file that grows with every session and is never auto-pruned. It reports four classes of bloat: dead projects[] keys, dead githubRepoPaths[*] worktree paths, orphaned disabledMcpServers[] entries, and bare-vs-namespaced duplicate MCP names. The audit is read-only: it prints suggested jq filters for the operator to run manually after closing other Claude Code sessions.

Concurrent-write warning. The harness rewrites ~/.claude.json on session end. Before acting on the audit's suggested cleanups, close every other Claude Code session — otherwise the in-memory state of a live session will clobber your edits when it next writes the file. An automated cleanup writer is out of scope for this audit.

Step 3: Report findings

Print a consolidated report grouped by scope:

1. Environment — plugins/settings/hooks/MCP status + counts, SessionStart smoke test, pre-commit validity, permissions coverage, marketplace enrollment 2. Registry — orphaned projectPath entries, stale enabledPlugins keys, registry-vs-settings drift 3. Stack — detected stack + relevant/irrelevant/missing plugin recommendations 4. Agentic — skills missing optimisation tables, bare CLI commands, stale reviews 5. Runtime~/.claude.json size, dead projects/githubRepoPaths, orphaned disabledMcpServers, duplicate MCP naming (read-only — no --fix path)

Use STATUS= indicators (OK/WARN/ERROR) and issue counts per scope. Include a summary table:

CheckStatusIssues
Plugin registryOK/WARN/ERROR...
Settings filesOK/WARN/ERROR...
Hooks configurationOK/WARN/ERROR...
MCP serversOK/WARN/ERROR...
SessionStart smoke testOK/WARN/ERROR...
Pre-commit configOK/WARN/ERROR/SKIP...
Permissions coverageOK/WARN/ERROR...
Marketplace enrollmentOK/WARN/ERROR...
Registry auditOK/WARN/ERROR...
Stack auditOK/WARN/ERROR...
Agentic auditOK/WARN/ERROR...
Runtime auditOK/WARN/ERROR...

See REFERENCE.md for the full report template.

Step 4: Apply fixes (if --fix)

If --fix is set:

1. If --scope=all AND findings exist in multiple scopes, use AskUserQuestion to let the user pick which scopes to fix (multi-select: registry, stack, agentic). 2. For each selected scope, delegate:

ScopeDelegate to
registrybash "${CLAUDE_PLUGIN_ROOT}/skills/health-plugins/scripts/fix-registry.sh" --home-dir "$HOME" --project-dir "$(pwd)" (pass --dry-run when set)
stackFollow the --fix flow in ${CLAUDE_PLUGIN_ROOT}/skills/health-audit/SKILL.md (Step 6)
agenticFollow the --fix flow in ${CLAUDE_PLUGIN_ROOT}/skills/health-agentic-audit/SKILL.md (Step 6)

3. Parse each script's output (STATUS=, REMOVED_COUNT=, MESSAGE=, RESTART_REQUIRED=) and report what changed. 4. If any fix reports RESTART_REQUIRED=true, remind the user to restart Claude Code.

Step 5: Verify

Re-run the relevant checks and confirm issue counts have dropped.

Agentic Optimizations

ContextCommand
Full scan/health:check
Registry only/health:check --scope=registry
Stack relevance only/health:check --scope=stack
Agentic audit only/health:check --scope=agentic
Runtime state audit (~/.claude.json)/health:check --scope=runtime
Fix everything (interactive)/health:check --fix
Dry-run preview of fixes/health:check --fix --dry-run
Detailed diagnostics/health:check --verbose
Check plugin registry existsfind ~/.claude/plugins -name 'installed_plugins.json'
Validate settings JSONfind .claude -maxdepth 1 -name 'settings.json'
Smoke-test install scriptCLAUDE_CODE_REMOTE=true bash scripts/install_pkgs.sh
Validate pre-commit configpre-commit validate-config .pre-commit-config.yaml
Check marketplace enrollmentfind .claude -maxdepth 1 -name 'settings.json' then grep for extraKnownMarketplaces

Known Issues

IssueSymptomFix path
#14202Plugin shows "installed" but not active/health:check --scope=registry --fix
Stale enabledPlugins key in settings.jsonPlugin appears enabled but no registry/marketplace entry/health:check --scope=registry --fix
Orphaned projectPathPlugin installed for deleted project/health:check --scope=registry --fix
Invalid settings JSONSettings file won't load/health:check
Missing marketplace enrollmentlaurigates/claude-plugins skills unavailable in web sessions/configure:claude-plugins --fix

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.