Content
85%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.
Highly actionable, executable content with well-sequenced workflows and strong validation checkpoints, at the cost of a monolithic single-file structure with no reference files and some cross-flow redundancy. Splitting stable reference material out of SKILL.md would address the weakest dimension.
Suggestions
Move the DeerFlow Review Heuristics, the Validation Guidance surface-to-command table, and the Output templates into one-level-deep reference files (e.g. references/heuristics.md, references/validation.md, references/output-templates.md), keeping SKILL.md as a routing overview.
De-duplicate the prior-coverage/net-new-delta rule: state it once in "Existing Coverage and Re-Runs" and have the Issue Flow and PR Flow prechecks reference it by name instead of restating it.
Consolidate the opener-writing guidance (Issue Flow step 4 and the PR review opener paragraph) into a single shared section to trim repeated instruction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence — no explanations of GitHub, git, or CI basics — and nearly every line instructs, but the net-new-delta/prior-coverage rule is stated in "Existing Coverage and Re-Runs" and re-stated in both the Issue Flow and PR Flow prechecks, and opener-writing guidance appears in both flows. That trimmable repetition keeps it just below the every-token-earns-its-place anchor. | 4 / 5 |
Actionability | Fully executable throughout: exact `gh issue/pr view --json <field list>` commands, `git fetch <base-remote> +refs/heads/...` and `BASE=$(git merge-base ...)` invocations, copy-paste comment and review templates, concrete P0/P1/P2 severity definitions, a surface-to-validation-command table, and concrete output templates — matching the copy-paste-ready anchor. | 5 / 5 |
Workflow Clarity | Sequences are explicit with validation checkpoints and feedback loops throughout — "Immediately before posting, refresh comments; fold any equivalent comment", "Re-check the head SHA immediately before posting... re-review the new diff or abort", and abort/failure paths for unreadable diffs. The batch-operation validation cap does not apply because validation steps are present. | 5 / 5 |
Progressive Disclosure | No bundle files exist and the entire skill is a single ~290-line monolith with good headers, but clearly separable material (DeerFlow Review Heuristics, the Validation Guidance table, the Output templates, the Diff Base Rule) is inlined in SKILL.md instead of one-level-deep reference files — matching the anchor where content that should be separate is inline. | 3 / 5 |
Total | 17 / 20 Passed |