skill-healthlisted

# skill-health — Skill-Library Structural Debt Scan Detect **skill technical debt** — library-level defects that do not break a single skill in isolation but degrade the library over time (SkillOps, Pu/Song/ Zhao 2026, [arXiv:2605.13716](https://arxiv.org/abs/2605.13716)). This skill owns the one debt pattern no other harness skill checks: **missing artifacts** — a SKILL.md that references a `scripts/` module, a `bash` script, an agent, or a sibling skill that no longer exists on disk (it silently dangles after a rename or delete). This is a **structural** property — decidable from the literal text plus a filesystem `exists()` check — so it is owned by deterministic code at 100% accuracy (AKC ADR-0008 Code-LLM Layering). The semantic, risk, and validation dimensions are **delegated, never re-implemented here**. ### Three output categories — only one is a defect claim The scanner reports three lists, and conflating them is the mistake this section exists to prevent: - **Dangling references** (`dangling`, exit code 1) — the skill wrote a *path*, and that path does not exist. `exists()` is authoritative here. - **Unresolved names** (`unresolved_names`, exit code unaffected) — the skill named a skill/command *without a path* (`See skill: X`, `` `X` skill ``, `` `/X` ``) and no file matches under the skills root. **This is an enumeration handed to judgment, not a finding.** The name may still be a CLI builtin, a bundled skill, a plugin command, or a project-scoped s