Content
65%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 admirably token-efficient and its acceptance criteria are unusually specific, but it reads as a flat checklist rather than an executable workflow: no commands for verifying criteria, no re-validation after fixes, and a machine-specific absolute path for the referenced pr-name skill. The limitations.mdx guidance is the strongest part, with a concrete file path and a clear keep/omit rule.
Suggestions
Add concrete verification commands (e.g. gh pr checks, gh pr view --json isDraft,reviewDecision, or git log for the last-hour push check) so each criterion is executable rather than merely stated.
Restructure into an ordered workflow with an explicit fix-then-revalidate loop: check criteria, push fixes if needed, re-run checks, and only merge when green again — the current batch-merge flow caps workflow clarity at 3 without it.
Replace the absolute path to the pr-name skill (/Users/jonathanburger/.codex/...) with a portable relative reference or inline the naming convention, and add a header for the criteria section so the two-part structure is navigable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean checklist of criteria plus two tight paragraphs of editing guidance; it assumes Claude's competence, explains nothing it already knows, and every token earns its place. | 5 / 5 |
Actionability | The criteria are individually checkable ("must be green", "must not be draft", "no pushes within last hour") and the limitations.mdx guidance names a concrete file and method, but there are no executable commands for verifying any criterion, and the "$pr-name" requirement points to an absolute path on one user's machine (/Users/jonathanburger/...) that cannot be followed elsewhere — concrete guidance with key details missing. | 3 / 5 |
Workflow Clarity | The instruction "merge PRs which satisfy criteria" implies an evaluate-then-merge sequence and the criteria act as implicit gates, but the flow is loosely sequenced: remediation actions ("you may push fixes", "you may resolve merge conflicts") are interleaved with checks, and there is no re-validation loop (e.g. re-check green after pushing). As a batch/destructive merge workflow without explicit validation checkpoints, it is capped at 3. | 3 / 5 |
Progressive Disclosure | At under 50 lines with no bundle files, the content itself needs no splitting, but structure is loose (a bare "criteria:" list with no header, one ## section) and its one reference to the pr-name skill is an external absolute path rather than a portable bundle-relative link — more than the 'minor organization gaps' of level 4. | 3 / 5 |
Total | 14 / 20 Passed |