Content
73%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 presents a clearly sequenced, well-validated five-phase workflow with genuinely concrete commands and thoughtful edge-case handling, so a competent executor knows exactly what to do. Its weaknesses are token efficiency — the core invariants are repeated many times and some meta-justification prose could be cut — and a posting step described in prose where a copy-paste command would be tighter. Instruction-only guidance is otherwise actionable enough that the absence of code blocks is not penalized.
Suggestions
State the fixed-lens panel invariant once (e.g. in the Pipeline Overview) and reference it elsewhere instead of restating it in the intro, 'Why this is a project skill', Caller Signature, When to Use, Phase 2, and Rules — this alone would cut meaningful tokens.
Replace the prose description of the JSON body construction with the actual copy-paste command, e.g. jq -n --rawfile body comment.md '{"body": $body}' | gh api repos/{owner}/{repo}/issues/{N}/comments --input -.
Delete execution-irrelevant meta-commentary (the /conduct activation-precondition justification, the repeated 'the diff headers are authoritative' restatements) and the basic diff-reading conventions explaining +/- lines, which Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The instruction content is real and dense, but the fixed-panel invariant is restated roughly seven times across sections, the "/conduct activation precondition" justification is execution-irrelevant meta-commentary, and "Diff-reading conventions: lines starting with + are added" explains what Claude already knows — mostly efficient but could be tightened considerably, anchor 3 rather than 2 since padding is redundancy rather than concept explanation. | 3 / 5 |
Actionability | Concrete executable commands appear throughout (gh pr view --json number, git status --porcelain, gh pr diff {N}, gh api repos/{owner}/{repo}/issues/{N}/comments) with precise shell-safety posting discipline, but the jq --rawfile JSON-body construction step is described in prose rather than given as a copy-paste command — mostly executable with minor gaps, anchor 4. | 4 / 5 |
Workflow Clarity | Five explicitly sequenced phases with real validation checkpoints: adversarial refutation with survival criteria (Phase 2b), the ≥80% confidence threshold, the Phase 3 direction-error guard, the untracked-file edge case, the trivial-change skip, and harness permission gating of the external write, plus a Rules checklist — matches the anchor-5 pattern of explicit validation with error-recovery handling. | 5 / 5 |
Progressive Disclosure | Well-organized single-file structure with clear section headers and no nested references, self-contained by design with no bundle files to navigate; however, at ~125 lines everything is inlined (beyond the under-50-line simple-skill exception), so this is good placement with minor organization gaps (anchor 4) rather than the ideal split of anchor 5. | 4 / 5 |
Total | 16 / 20 Passed |