Conciseness

The body is lean and directive throughout: 'Measure the handoffs, not the keystrokes', 'unavailable inputs are reported as unavailable, never estimated', 'No composite scores: do not blend indicators into a single productivity number'. It never explains what DORA or git is, assumes Claude's competence, and every section prescribes rather than pads.

Actionability

Guidance is concrete and executable for an instruction-only skill: exact metric definitions ('Change failure rate: deploys needing hotfix or rollback, divided by deploys'), concrete paths ('docs/ops/bands.yaml', 'artifacts/sdlc-metrics.md'), and a per-stage indicator table. Not anchor 5 because a few table indicators such as 'defect escape rate' and 'eval pass rate' are named without a derivation rule in either the body or the schema reference.

Workflow Clarity

The reporting workflow is well structured — emit at 'a workflow terminal state, alongside artifacts/session-cost.md', 'Load references/metrics-schema.md for the report skeleton', band 'Detection is deterministic and computed before any agent reads the signal' — with report-time checkpoints (cite source, mark unavailable, trend vs previous). Not anchor 5 because the gather → derive → emit sequence is implicit in sections rather than stated as an ordered procedure.

Progressive Disclosure

The body is an overview contract that delegates detail at the right depth: 'Load references/metrics-schema.md for the report skeleton' and 'Schema: references/bands-template.yaml', both real files in the bundle, confirmed one level deep with no further nested references, plus a clean References section. Content is appropriately split between the contract body, the report skeleton, and the bands template.

Specificity

The description names several concrete capabilities — 'Define the delivery metrics contract', 'DORA four plus per-stage indicators derived from artifact and git history', 'the control bands that turn metric drift into a routed intake' — rather than vague language. It stops short of anchor 5 because emission of the report artifact and unavailable-input handling are covered only in the body, leaving minor coverage gaps.

Completeness

It explicitly answers both parts: 'Define the delivery metrics contract for agent-assisted SDLC — DORA four plus per-stage indicators... and the control bands...' (what) and 'Use when reporting cycle time, plan adherence, or defining response thresholds' (when, with concrete trigger phrases). This matches the anchor-5 good example's structure exactly.

Trigger Term Quality

It carries good natural terms a user would say: 'delivery metrics', 'cycle time', 'plan adherence', 'response thresholds', 'DORA'. Not anchor 5 because common variations users might say — 'lead time', 'change failure rate' — appear only in the frontmatter metadata triggers, not the description itself.

Distinctiveness Conflict Risk

The niche is clear — agent-assisted SDLC delivery metrics with DORA and control bands — with triggers specific to that domain. Not anchor 5 because terms like 'cycle time' and 'response thresholds' have minor overlap risk with generic observability or CI-metrics skills.