Stability Score

One repeatable pass that keeps fak trustworthy while it iterates fast — the question no other scorecard asks: as we add items quickly, how do we KNOW a regression / tail-wag / confusion landed, and how do we REVERT to a stable version? Runs the stability scorecard (tools/stability_scorecard.py) over the git-tracked tree across four groups — sentinel (a regression turns a gate RED), invariant (the core assumptions are encoded as tests), revert (we can roll back: keep/revert ladder, version pin, CI-gated tags, a documented rollback runbook), and drift (a small thing wagging a big thing gets caught) — turns each HARD defect into a required affordance to ADD (wire the missing CI regression gate, encode the missing invariant test, commit the missing ratchet baseline, write/link the rollback runbook), retires stability-debt worst-first, re-measures + regenerates the snapshot to PROVE the debt dropped, and commits only the scorecard lane by explicit path. The stability counterpart of code-quality (defects) and rsi-maturity (the self-improver's structure). Use after a change to a CI gate, an invariant test, a baseline, the release/rollback path, or on a /loop cadence to keep the trunk safe to move fast on.

mkdir -p ~/.claude/skills/stability-score
curl -L https://claudskills.com/skills/stability-score/SKILL.md \
  -o ~/.claude/skills/stability-score/SKILL.md

@misc{stability-score-2026,
  author    = {anthony-chaudhary},
  title     = {Stability Score [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/stability-score/}
}