Conciseness

The body is lean and operative throughout — e.g. "Run `scripts/validate-standard.sh` for a read-only report" — with zero padding or explanation of known concepts. Not 5 because the `refresh/refresh-consumer.sh` table cell compresses ~25 operational rules into one run-on paragraph where brevity starts to sacrifice clarity.

Actionability

Concrete, executable commands are given: `gh pr edit <PR#> --add-reviewer @copilot`, `gh pr merge <N> --admin --match-head-commit <SHA>`, `fleet repos kendex-refresh`, plus a numbered 4-step bypass procedure. Not 5 because the `refresh/*.sh` scripts lack exact invocation syntax (arguments, checkout steps) and depend on external skill docs for orch/github paths.

Workflow Clarity

Validation checkpoints are explicit — "reads both rulesets back" after adding and removing bypasses, "Confirm that the arm enabled auto-merge", "Wait for GitHub to show the published head" — and error paths are enumerated ("A failed direct merge reports `refresh-error=merge`"). Not 5 because the refresh workflow's branching conditions (bypass-present vs not, armed/disarmed states) are compressed into prose and a table cell rather than a clearly sequenced step list.

Progressive Disclosure

The body is an overview with well-signaled, one-level-deep references to real files: [references/adoption.md](references/adoption.md) with specific section anchors (all verified present), [references/vendored-paths.md](references/vendored-paths.md), and a scripts table pointing to actual bundle scripts. Not 5 because the refresh-consumer behavior spec is inlined in a table cell rather than split to a reference, and several paths point outside the bundle (release checkout, orch/github skills).

Specificity

Names the domain and two actions — "report the organization standard" and "adopt consumer refresh" — matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. Not 4 because only two terse actions are listed with no elaboration of what the standard or refresh actually cover.

Completeness

A 'what' is present ("report the organization standard or adopt consumer refresh") but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the guidelines. Not 2 because the 'what' names two concrete operations rather than being extremely vague; not 4 because 'when' is entirely absent.

Trigger Term Quality

"organization standard" and "consumer refresh" are internal jargon; a user needing this skill would more naturally say "review rules", "approvals", "rulesets" or "refresh the consumer install" — none appear. Fits anchor 2 ('One or two generic keywords; missing the natural phrases users say') rather than 3, which requires a broader set of relevant keywords.

Distinctiveness Conflict Risk

The niche is genuinely specific (org-standard reporting plus a named consumer-refresh flow), so overlap risk with other skills is minor — anchor 4. Not 5 because no concrete distinct trigger phrases are given and "organization standard" could superficially overlap generic standards/compliance skills.