Content
42%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 well-organized into clear sections and appropriately brief, but it is essentially a generic outline: instructions are high-level directives with no templates or examples, redundant filler sections pad the token budget, and the single external reference points to a file missing from the bundle. A reviewer following this skill would know the shape of the output but not how to produce a good one.
Suggestions
Fix the dangling reference: either ship `resources/implementation-playbook.md` with the bundle or inline a minimal PR description template and checklist so the guidance is self-contained.
Make instructions concrete — include one worked example of a PR description (what/why/tests/risks sections) and specify what the reviewer checklist should contain, instead of directives like "Summarize changes, tests, and risks clearly".
Cut the filler: remove the "You are a PR optimization expert" preamble, the "Context" section (duplicates the Use-when list), and the empty "Requirements" section to tighten token efficiency.
Number the instruction steps and state when to consult the playbook, giving the workflow an explicit order and a decision point.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and free of concept over-explanation, but it restates the skill's purpose three times (intro paragraph, "Use this skill when", "Context") and includes filler sections like "Requirements: Take the requirements, target, and scope from the user's request", so it could be tightened considerably. | 3 / 5 |
Actionability | Instructions are high-level hints ("Summarize changes, tests, and risks clearly", "Add checklists and reviewer guidance") with no example PR description, template, or checklist format, and the one concrete pointer to templates ("If detailed templates are required, open `resources/implementation-playbook.md`") targets a file that does not exist in the bundle, leaving minimal executable guidance. | 2 / 5 |
Workflow Clarity | Steps are listed in a rough implied order (analyze diff, summarize, highlight breaking changes, add checklists) and the Output Format section defines the deliverable, but the sequence is unnumbered, has no validation checkpoints, and gives no guidance on when the playbook should actually be used; this is not a destructive or batch operation so no lower cap applies. | 3 / 5 |
Progressive Disclosure | The body is well-sectioned and appropriately lean, and the single reference ("resources/implementation-playbook.md for detailed templates and examples") is clearly signaled in both Instructions and Resources — but that file is absent from the bundle (no references/, scripts/, assets/, or resources/ directories exist), so the promised one-level-deep detail layer is unreachable, a clear organization gap that keeps this below anchor 4. | 3 / 5 |
Total | 11 / 20 Passed |