Content
100%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 body is an instruction-only skill executed superbly: concrete gh/git commands for every step, an explicit gather-triage-fix-push loop with stop conditions and feedback loops, untrusted-input handling (Rule 0) up front, and validation before acting (verify findings against source, base-red check, resolve-after-reply). No padding, no concept explanations, no pseudocode — every rule is load-bearing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence throughout — no explanation of what CI, rebasing, or GitHub review threads are; every line is a rule or command ('Never get green by deleting an assertion, adding a skip, or --no-verify'). It matches the 'every token earns its place' anchor; the 4 anchor's 'minor instances of over-explanation' are absent. | 5 / 5 |
Actionability | Commands are copy-paste ready and cover the common cases: `gh pr checks "$PR" --watch`, a complete graphql query with a --jq filter for unresolved threads, `gh run view <run-id> --log-failed`, `gh run rerun --failed`, `git fetch/rebase/push --force-with-lease`, and a reply template. The only placeholders (<owner>, <repo>, <run-id>) are trivially filled, so this fits the fully-executable anchor better than the 4 anchor's 'minor gaps'. | 5 / 5 |
Workflow Clarity | The loop is explicit ('gather → triage → fix → push once → report in one line') with hard stop conditions ('Stop after 10 passes, or 3 passes with nothing new'), feedback loops (fix→re-check, rerun at most twice, stop after two different fixes), and validation checkpoints (verify every bot finding against the source, check whether the base branch is red, resolve threads only after replying). The destructive/batch cap at 3 does not apply because validation steps are present throughout. | 5 / 5 |
Progressive Disclosure | The skill is a self-contained single-process workflow with no bundle files and nothing that belongs in a separate file; it is organized into tight labeled sections (Rule 0, Setup, the loop, CI failures, bot/human comments, branch currency, replying, Never, Report) that make navigation trivial. This matches the well-organized, appropriately-placed top anchor; per the no-external-references guidance, a skill with no need for separate files can score 5 on section organization alone. | 5 / 5 |
Total | 20 / 20 Passed |