Content
75%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 well-structured, executable skill: concrete git/test commands, a specific slop catalogue, guardrails, and a validated code-mode workflow. Weaknesses are second-mode support (skill-file mode lacks a workflow and verification), a dangling external reference, and minor duplication between the Trigger, workflow, and Output sections.
Suggestions
Add a short numbered workflow for skill-file mode mirroring the code-mode sequence, ending with a verification step (e.g., re-read the linted SKILL.md to confirm flagged issues were fixed) — the skill's own "premature stop" flag applies to it.
Fix or internalize the reference to `../../rules/skill-conventions.mdc`: the target does not exist in the skill bundle; either inline the needed convention rules or move them to a `references/` file inside the bundle.
Remove duplication: the Trigger section repeats the frontmatter description's "before committing" guidance, and workflow step 6 "Summarise what was cleaned" restates the Output section — keep one source of truth.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean, terse bullets with no explanation of concepts Claude already knows ("Casts to `any` used only to bypass type issues", "Three similar lines of code is better than a premature abstraction"). Minor trims remain: the Trigger section duplicates the frontmatter description, and "Summarise what was cleaned" (step 6) overlaps the Output section. Anchor 4, not 5. | 4 / 5 |
Actionability | Copy-paste ready commands ("git diff origin/main...HEAD", "npm test -- --changed --passWithNoTests 2>&1 | tail -10") and a concrete slop catalogue ("renamed `_vars`, re-exports, `// removed` comments"). Minor gaps: no before/after slop-to-clean example, and the test command assumes an npm project. Anchor 4 rather than 5. | 4 / 5 |
Workflow Clarity | Code mode has a clear 6-step sequence with explicit validation ("Re-run `git diff origin/main...HEAD` to verify only slop was removed"; run tests/type-check), but skill-file mode has no sequenced steps or verification — ironic given the skill itself flags "premature stop: cleans but never verifies". Anchor 4, not 5. | 4 / 5 |
Progressive Disclosure | Well-organized sections with a single clearly signaled one-level reference ("See [`rules/skill-conventions.mdc`](../../rules/skill-conventions.mdc)"). Minor gaps: that path points outside the skill bundle and the target file is absent from this bundle, and the ~80-line body runs past one screen. Anchor 4; above 3 since the reference is clearly signaled and nothing that belongs in a separate file is inlined. | 4 / 5 |
Total | 16 / 20 Passed |