Needs Attention Internal

Compose the livespec-fleet-DEVELOPMENT signals a fleet maintainer must watch but an end user does NOT control — CI red on any fleet repo, fleet-conformance drift, stale cross-repo pins, cross-repo consistency drift, and ledger status-conformance drift — into one point-in-time attention list. It mostly reads signals already computed elsewhere (GitHub Actions for CI, the dev-tooling conformance and pin-freshness checks, `/livespec:doctor` for drift); the one exception is the ledger status-conformance scan, which runs a cheap per-tenant `ledger-normalize --dry-run` directly because no scheduled workflow computes it. All are normalized into the shared `attention_item` shape with `kind: "internal"`. This is the internal sibling of the shipped product `needs-attention`: the dividing test is *does an end user have actionable control?* — yes routes to the shipped `needs-attention` (plugin version, their repo's hygiene), no routes here (fleet CI/conformance/pins/drift). LOCAL-ONLY to livespec core, maintainer-only, UNSYNCED — it is not part of the livespec plugin, the spec, the copier template, or any fleet-propagated surface, and never ships to the plugin or to adopters. Emits nothing when the fleet is green.

mkdir -p ~/.claude/skills/needs-attention-internal
curl -L https://claudskills.com/skills/needs-attention-internal/SKILL.md \
  -o ~/.claude/skills/needs-attention-internal/SKILL.md

@misc{needs-attention-internal-2026,
  author    = {thewoolleyman},
  title     = {Needs Attention Internal [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/needs-attention-internal/}
}