Content
40%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-structured with clear use/don't-use and output-format sections, but its instructions are generic boilerplate with no executable guidance or concrete examples, and it points to a resources file that is absent from the bundle.
Suggestions
Replace generic instructions with concrete, executable steps (e.g., specific commands or a PR-description template with worked examples) to raise actionability.
Add explicit validation checkpoints (e.g., verify description against the diff, confirm test coverage delta) to give the workflow a real feedback loop.
Either provide resources/implementation-playbook.md or remove the broken reference so progressive disclosure is fully sound.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is relatively short and sectioned, but it repeats the frontmatter description verbatim in the intro and includes generic boilerplate ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.') that could be tightened. | 3 / 5 |
Actionability | Guidance is high-level and abstract ('Apply relevant best practices', 'Provide actionable steps and verification') with no concrete code, commands, templates, or worked examples; the only concrete pointer is to a missing file. | 2 / 5 |
Workflow Clarity | A rough sequence is implied (clarify goals -> apply practices -> validate), but steps are poorly defined and validation is mentioned only abstractly with no concrete checkpoints or feedback loops. | 2 / 5 |
Progressive Disclosure | Content is well-organized into clear sections with a single one-level-deep reference ('resources/implementation-playbook.md') signaled in both Instructions and Resources, but the referenced file does not exist, a minor organization gap. | 4 / 5 |
Total | 11 / 20 Passed |