Content
92%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.
A strong, highly actionable orchestration skill: exact commands and scripts, a clearly sequenced multi-phase workflow with validation, feedback loops, and escalation limits, and clean progressive disclosure to verified bundle files. The only flaw is deliberate repetition of the PO/worker boundary and status-vs-content rules across three sections, which costs it the top conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Efficient and workflow-specific — no space is spent explaining git/CI/codex concepts Claude already knows, and templates, shell recipes, and pitfalls are offloaded to bundle files. However, the orchestrator-boundary rule ("Claude never edits source files, never reads diffs for judgment") and the status-vs-content distinction are each repeated about three times (orchestration model, review wave, and Key pitfalls), which is trimmable repetition. This fits anchor 4 ('minor instances of over-explanation that could be trimmed') better than 3, since the rest is dense with non-obvious operational knowledge, and better than 5, since 'every token earns its place' is violated by the deliberate repetition. | 4 / 5 |
Actionability | Fully executable guidance throughout: exact commands (`gh pr view <N> --json statusCheckRollup,mergeable,mergeStateStatus,headRefOid`, `git diff origin/main...origin/<branch> --stat`), concrete scripts with argument signatures (`scripts/merge_and_cleanup.sh <PR> <worktree-path> <branch>`, `scripts/wait_for_ci.sh <PR>`), exact worktree/branch naming conventions, a precise log-line format with field semantics, and a copy-paste archival shell snippet. Prompt composition steps delegate to a real, verified template file. Matches the copy-paste-ready top anchor. | 5 / 5 |
Workflow Clarity | Clear four-phase sequence (dispatch → monitor → review wave → correction wave → merge + cleanup) with explicit validation checkpoints at every phase: PR existence/CI checks with exact commands, malformed-JSON handling, read-only enforcement verification, verification of log-vs-committed conflict markers via `gh pr diff`, and a defined feedback loop (corrector → re-dispatch reviewer) with an escalation cap after 3 cycles. The conflict-triage checklist and Success criteria audit section complete the pattern. As a batch operation it fully satisfies the validation requirement, so no cap applies. | 5 / 5 |
Progressive Disclosure | The body is a well-organized orchestration overview that offloads detail to real, verified, one-level-deep bundle files with clear signals: "See `references/prompt-template.md` for the shape", "See `references/common-commands.md` for the exact shell recipes", and "See `references/pitfalls.md` for the full list. The top items:". All five referenced files (three references, two executable scripts) exist with substantive matching content, and no reference chain nests deeper than one level. The inlined reviewer checklist is appropriately inlined since it must be pasted verbatim into reviewer prompts. | 5 / 5 |
Total | 19 / 20 Passed |