Content
25%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 dominated by generic boilerplate that would apply to any skill, with the Output Format list as the only PR-specific content. Its reliance on a nonexistent playbook file means the skill defers all concrete examples to a resource the bundle never ships.
Suggestions
Fix the broken progressive disclosure: either ship `resources/implementation-playbook.md` in the bundle or remove both references and inline the key patterns/templates directly.
Replace the generic Instructions bullets with PR-specific sequenced steps (analyze the diff, draft each output section, run before/after coverage comparison, verify checklist items) that include explicit validation checkpoints.
Delete the filler sections ("Use this skill when", "Do not use this skill when", "Requirements") that duplicate the frontmatter description, and add one concrete example of a well-structured PR description so the guidance is executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | "Use this skill when", "Do not use this skill when", "Context", and "Requirements: Take the requirements, target, and scope from the user's request" are padded sections that duplicate the frontmatter or state nothing — several unnecessary padded sections. Not 3 because the filler spans most sections rather than being minor trimming; not 1 because nothing over-explains known concepts. | 2 / 5 |
Actionability | Only the Output Format list ("Executive summary with key metrics", "Before/after coverage comparison") is concrete; "Apply relevant best practices and validate outcomes" and "Provide actionable steps and verification" are generic hints — minimal concrete guidance missing the specific steps to execute. Not 3 because no template, example, or command appears anywhere in the body. | 2 / 5 |
Workflow Clarity | A rough generic sequence exists ("Clarify goals... Apply relevant best practices and validate outcomes. Provide actionable steps and verification.") but the steps are poorly defined, PR-specific steps are absent, and validation is only gestured at. Not 3 because the listed steps are one-line boilerplate that would fit any skill, with no real checkpoints. | 2 / 5 |
Progressive Disclosure | The sole reference, `resources/implementation-playbook.md`, is clearly signaled and one level deep but does not exist in the bundle (no resources/ directory is present), so the promised "detailed patterns and examples" are unreachable — the disclosure structure collapses in practice, landing noticeably below the midpoint. Not 1 because the body itself has clear section headers and is not a wall of text. | 2 / 5 |
Total | 8 / 20 Passed |