mcpbeat Sign in

Brooks Health Agent Skill

by hyhmrright

> Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).

1k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1313
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/hyhmrright/brooks-lint --skill brooks-health

What comes with it

3 834 bytes besides the instruction
health-guide.md

The instruction itself

3 sections, as written by the author

Brooks-Lint — Health Dashboard

Setup

Read in order:

  • ../_shared/common.md — Iron Law, Project Config, Report Template, Health Score
  • ../_shared/source-coverage.md — book coverage, exceptions, tradeoffs
  • ../_shared/decay-risks.md — production risk symptoms
  • ../_shared/test-decay-risks.md — test risk symptoms
  • health-guide.md (this directory) — the dashboard orchestration process

Process

Scope: if the user did not specify a project or directory, apply Auto Scope Detection

(../_shared/common.md) first.

  • Run abbreviated scans across all four dimensions (Step 1 of the guide)
  • Compute per-dimension and composite Health Scores with weighting (Step 2 of the guide)
  • Output the Health Dashboard using the dashboard report template (Step 3 of the guide)

Mode line in report: Health Dashboard

How to use it

Copy the folder

Take hyhmrright/brooks-health from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.