mxhealth

name: mxHealth description: Use when the user says "/health", "/mxHealth", "health check", "check knowledge db", "verify consistency", "db health", or otherwise wants to verify Knowledge-DB and docs/ consistency via MCP. Runs 14 consistency checks (document metadata, cross-references, orphaned relations, status consistency, CLAUDE.md weight, local/DB sync, AI-Steno format, skill-evolution metrics, AI-Batch status) and persists findings via Skill Evolution. Loop-capable. ⚡ MCP-required — aborts if Knowledge-DB is unreachable. allowed-tools: Read, Write, Edit, Grep, Glob, Bash

/mxHealth — Knowledge-DB Consistency Checker (AI-Steno: !=forbidden →=use ⚡=critical ?=ask)

Context: ALWAYS run as subagent(Agent-Tool) !main-context. Result: max 20 lines, problems only.

Health-Check-Agent. Verify consistency of Knowledge-DB + local docs/.

Trigger phrases

This skill fires on:

• /health, /mxHealth
• Natural language: "health check", "check knowledge db", "verify consistency", "db health", "audit the project state"
• Programmatic: pre-release validation, periodic /loop invocation, pre-commit integrity sweep

MCP Required

⚡ mxHealth is MCP-dependent by design. Phases P1-P14 all query the Knowledge-DB. If mx_ping fails in Init step 2 → print "MCP unreachable — /mxHealth requires MCP." and ABORT. No partial runs, no local-only fallback mode. The caller should retry once MCP is back.

Init

1. CLAUDE.md→**Slug:**=project. ∅slug→?user
2. mx_ping()→OK=continue | Error→"MCP unreachable — /mxHealth requires MCP." ABORT

Phase 1: Load Inventory

Execute in parallel:

1. mx_briefing(project) — Overview
2. mx_search(project, doc_type='plan') + spec + decision + workflow_log
3. Glob local: docs/reference/*.md
4. Read CLAUDE.md + docs/status.md
5. Count: DB-Docs total, local reference files, CLAUDE.md line count

Phase 2: 14 Checks

Per-check details (trigger, what is checked, severity, persistence target) → Read ~/.claude/skills/mxHealth/references/checks.md.

ERROR vs WARNING is binding: ERROR = invariant violation (must fix); WARNING = drift/risk (should fix); INFO = advisory (no persistence).

Phase 3: Report

## /mxHealth Report — YYYY-MM-DD HH:MM
**Project:** <slug> | **Scope:** <all|decisions|plans|specs|workflows>

### DB Inventory
| doc_type | Count |
|----------|-------|

### Findings
| # | Severity | Check | Finding | Document |
|---|----------|-------|---------|----------|

### Summary
X ERROR | Y WARNING | Z INFO | Checked: N DB docs, M local files

∅problems→/mxHealth: All checks passed. DB+docs/ consistent.

Phase 3b: Persist Findings→MCP Notes (Spec#1139)

For each finding with severity ERROR or WARNING:

1. Deduplication: mx_search(project, doc_type='note', query='[Health]