knip

Run knip to find and remove unused files, dependencies, and exports. Use for cleaning up dead code and unused dependencies.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/knip/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable guide with explicit feedback loops and confidence-based guardrails for a destructive workflow. Minor tightening and an explicit post-cleanup verification step would push it to the top anchor.

Suggestions

Add an explicit verification checkpoint after destructive fixes (e.g. re-run the project's build/tests to confirm nothing broke) to strengthen workflow validation.

Dedupe the 'knip does not handle unused imports/variables' note and the repeated command list in Common Commands to tighten conciseness.

Consider moving the Configuration Best Practices and/or Common Commands sections into a reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence, with only minor redundancy (the 'knip does NOT remove unused imports' note is repeated in Setup and Notes, and Common Commands re-shows already-demonstrated commands).	4 / 5
Actionability	Copy-paste ready commands throughout (`npx knip`, `--production`, `--fix`, `--fix --allow-remove-files`, `--reporter json`) plus concrete config snippets like `ignoreExportsUsedInFile: { interface: true, type: true }` cover the common cases.	5 / 5
Workflow Clarity	A clear 6-step sequence with feedback loops (re-run knip after each config change until hints resolve; re-run after each fix batch) and ask-first guardrails, but it lacks an explicit post-deletion build/test verification checkpoint for destructive removals.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and good navigation, but at ~145 lines some inline material (Common Commands, Configuration Best Practices) could be split into reference files.	4 / 5
	Total	17 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is clear, actionable, and includes an explicit trigger clause, naming knip and its core cleanup targets. It is solid but could reach the top anchor with broader coverage and more concrete user-facing trigger phrasing.

Suggestions

Add a concrete 'Use when the user mentions...' trigger phrase listing natural terms (e.g. 'unused dependencies', 'dead code', 'unused exports') to lift completeness.

Mention unused types alongside files, dependencies, and exports for more comprehensive specificity.

Clarify the boundary from linters (e.g. 'not for unused imports/variables') to reduce overlap risk with lint/cleanup skills.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('find and remove unused files, dependencies, and exports') covering knip's main categories, but stops short of comprehensive coverage (e.g. unused types) matching the 5 anchor.	4 / 5
Completeness	Provides a clear 'what' ('Run knip to find and remove unused files, dependencies, and exports') and an explicit 'Use for' trigger, but the 'when' clause is less specific than the 5-anchor's concrete user-phrasing triggers.	4 / 5
Trigger Term Quality	Includes natural user phrases like 'cleaning up dead code', 'unused dependencies', and 'unused files', with good keyword coverage though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Leading with the named tool 'knip' gives a clear niche, though 'cleaning up dead code' carries minor overlap risk with general linter/cleanup skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: brianlovin/agent-config
Path: skills/knip/SKILL.md
Commit: 1a9819e

Reviewed: ~3 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.