mxHealth

Run 14 automated checks to validate Knowledge-DB and documentation integrity via MCP.

29|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/MicrotronX/mxLore --skill mxhealth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mxHealth
Source: https://github.com/MicrotronX/mxLore/tree/main/claude-setup/skills/mxHealth
Command: npx skills add https://github.com/MicrotronX/mxLore --skill mxhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification of Knowledge-DB and documentation integrity across projects via MCP, by running a comprehensive suite of checks to detect inconsistencies and gate issues before release.

Core Features & Use Cases

  • 14 automated checks covering document metadata, cross-reference integrity, orphaned relations, status consistency, CLAUDE.md weight, local vs. DB synchronization, AI-Steno format, and AI-Batch status, with findings persisted via Skill Evolution.
  • Loop-capable health sweeps that can be triggered during development cycles to maintain an up-to-date view of knowledge health.
  • MCP-required workflow ensures authoritative data and guardrails; aborts if MCP is unreachable to avoid partial results.

Quick Start

Send /health to mxHealth to run the Knowledge-DB consistency checks.

Frequently Asked Questions about mxHealth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check documentation consistency and Knowledge-DB integrity in MCP projects?

Documentation consistency and Knowledge-DB integrity are checked by running 14 automated validation checks that verify metadata, cross-references, and local synchronization across MCP-enabled projects.

What is a Knowledge-DB health check and what does it validate?

A Knowledge-DB health check is an automated audit that validates document metadata, cross-reference integrity, orphaned relations, status consistency, CLAUDE.md weight, AI-Steno formatting, and AI-Batch status.

Do I need MCP to run knowledge database consistency checks?

MCP is required for running knowledge database consistency checks. The process aborts if MCP is unreachable to ensure authoritative data and prevent partial results.

How do I run a health sweep to detect documentation inconsistencies?

Trigger a health sweep by sending the /health command. This initiates loop-capable checks that query the Knowledge-DB, aggregate findings, and persist results via Skill Evolution.

What happens if local docs and the database are out of sync during an audit?

During an audit, local vs. DB synchronization is explicitly verified. The automated checks detect this mismatch, aggregate the finding, and report it to maintain knowledge health.

Why does my Knowledge-DB audit abort and not return results?

Your Knowledge-DB audit aborts to avoid partial results when MCP is unreachable, ensuring that guardrails and authoritative data are present before performing the 14 consistency checks.