Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The core gating content is exemplary — terse, decision-oriented, and copy-paste executable with named real-workflow examples. The skill is undermined by its bundle: the entire ordered-image-release section leans on a references/ordered-image-releases.md file that is absent, leaving that use case non-actionable and its dense policy prose unsupported.
Suggestions
Ship the missing references/ordered-image-releases.md (including the referenced 'bound work before activation' anchor) or inline its essential steps — the body currently directs a primary use case to a nonexistent file.
Add an explicit pre-merge validation step, e.g., verify `CD_DEPLOY_ENABLED` is set on the intended deploy repo before merging, complementing the existing `actionlint` lint guidance.
The ordered-image section uses undefined jargon ("destination frontier", "seed and consumer binding"); define these inline or ensure the restored reference introduces them before use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and operational throughout — gate/don't-gate lists, the decision test ("The test is 'pushes a prod image or triggers a deploy' — not 'builds on master'"), copy-paste gate patterns, and terse policy facts like "A receipt proves the origin, not regional availability". Nothing explains concepts Claude already knows, and every token carries repo-specific information. Matches the 5 anchor; there is no padding to trim for 4. | 5 / 5 |
Actionability | The gating guidance is fully executable — five copy-paste-ready `if:`/`push:` YAML variants covering whole-job, master-keyed, mixed PR+master, push-step, and reusable-input cases, plus named example workflows and an `actionlint` lint command. It falls short of 5 because the ordered-image-release use case (named in the description) has no executable steps in the body and defers entirely to a reference file that is missing from the bundle. | 4 / 5 |
Workflow Clarity | A clear sequence is present: apply the decision test, pick the matching gate pattern, "Set CD_DEPLOY_ENABLED on the repo that should ship **before merging**, or master pushes skip the build/deploy", then "Lint with `actionlint`" — a concrete validation checkpoint. Minor gaps (no step verifying the variable is actually set on the target repo, no fix-and-retry loop) keep it at the 4 anchor rather than 5. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned and the reference is clearly signaled ("read [Ordered image releases](references/ordered-image-releases.md)" plus an anchor link), but the bundle contains no `references/` directory — the linked file does not exist. Since a primary use case depends on that dangling reference, navigation is broken rather than merely imprecise, matching the 2 anchor's structurally deficient organization; it is not a 3, where references are at least real but weakly signaled. | 2 / 5 |
Total | 15 / 20 Passed |