Content
82%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 tight, command-driven skill: every section is executable, the entry-vs-project concept is explained in two lines, and pitfalls (auto-fix, brownfield rollout) are addressed as an anti-patterns table. The only gaps are cosmetic duplication and the absence of an explicit post-cleanup verification loop.
Suggestions
Trim duplication for conciseness: drop the "When to use" bullets that restate the description's triggers and collapse the three repeated "Per the [Knip docs]" citations into the single References-section link.
Close the workflow validation gap: after triage/deletion, add an explicit re-run step (e.g., "Re-run `npx knip` and confirm exit code 0 before declaring the project clean").
Move the per-framework plugin snippets in Step 4 (Next.js, Playwright configs) into a reference file so SKILL.md stays a lean overview with well-signaled one-level-deep references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and operational throughout — no explanations of what dead code is or how import-graph analysis works — but the "When to use" section restates the frontmatter triggers, "Per the [Knip docs]" is repeated three times, and plugin names are listed inline and again in References, so minor trims remain (anchor 4, not 5). | 4 / 5 |
Actionability | Every step ships copy-paste-ready material: `npm init @knip/config`, `npm install -D knip typescript @types/node`, a complete `knip.json`, `npx knip --max-show-issues 5`, `npx knip --no-exit-code > knip-baseline.txt`, CI YAML, and a triage table with per-issue actions (`npm uninstall`, `tags: ["public"]`) — clearly the fully-executable anchor. | 5 / 5 |
Workflow Clarity | Steps 1–7 are clearly sequenced and validation is present (exit-code semantics in Step 3, baseline-before-CI in Step 6, triage table marking which findings need review before deletion), but there is no explicit re-run-to-confirm-clean loop after cleanup — a minor checkpoint gap that fits anchor 4 rather than 5. | 4 / 5 |
Progressive Disclosure | A single ~160-line file with clear step headers, tables, and a References section linking the Knip docs and plugins page; structure and navigation are good, but nothing is split out (e.g., the per-framework plugin configs in Step 4) and the skill exceeds the under-50-lines case that would let well-organized sections alone score 5. | 4 / 5 |
Total | 17 / 20 Passed |