Content
57%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.
A lean, well-sectioned instruction-only skill with sensible safety constraints and a defined output format, and no padding that explains known concepts. Its weaknesses are abstract, non-executable instructions, implicit validation checkpoints without feedback loops, and a Resources reference to a playbook file that is missing from the bundle.
Suggestions
Fix the broken reference: resources/implementation-playbook.md does not exist in the bundle — either add the playbook file (typically under references/) or remove the two pointers to it.
Make Instructions executable: specify how to identify refactor candidates (duplication, long functions, high coupling), and give the concrete validation command(s) to run per step instead of the generic "Validate with tests and targeted regression checks".
Convert the flat instruction bullets into a sequenced workflow with explicit validation gates (e.g. "after each step, run the test suite; fix and re-run before proceeding") to add the missing feedback loop for batch code changes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Quote: "You are a code refactoring expert specializing in clean code principles..." and "The user needs help refactoring code to make it cleaner, more maintainable...". The body is short and assumes Claude's knowledge (never explains SOLID or refactoring concepts), but the persona opener and the Context/Requirements sections largely restate the frontmatter description — minor trimmable padding matching anchor 4 rather than anchor 5's every-token-earns-its-place. | 4 / 5 |
Actionability | Quotes: "Identify high-impact refactor candidates and risks", "Validate with tests and targeted regression checks", "If detailed patterns are required, open resources/implementation-playbook.md". Some concrete guidance structures the task, but no step carries criteria, commands, or examples, and the deferred detail points to a file absent from the bundle — incomplete guidance fitting anchor 3 rather than anchor 4's mostly-executable level. | 3 / 5 |
Workflow Clarity | Quotes: "Identify high-impact refactor candidates" → "Break work into small, testable steps" → "Apply changes" → "Validate with tests and targeted regression checks". A logical sequence with validation mentioned exists, but checkpoints are implicit rather than explicit gates and there is no validate-fix-retry feedback loop for batch code changes, matching anchor 3 ("sequence present but checkpoints missing or implicit"). | 3 / 5 |
Progressive Disclosure | Quote: "resources/implementation-playbook.md for detailed patterns and examples". Sections are well organized and the single reference is clearly signaled in a dedicated Resources section, but that file does not exist in the bundle (no resources/, references/, scripts/, or assets/ directories exist), leaving the promised detail unreachable — more than anchor 4's "minor organization gaps", though above anchor 2's buried-reference/inlined-content problems. | 3 / 5 |
Total | 13 / 20 Passed |