CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/knip-dead-code

Run Knip against a JS/TS project to detect unused files, unused dependencies, unused exports, and unused class/enum members. Scoped to production code; tests are entry-point-aware via Knip's framework plugins. Use after a feature or route is deleted and the project still compiles, or when `package.json` has accumulated dependencies nobody can account for.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-structured, actionable skill body that walks through install-to-CI-gate with executable commands and a triage/anti-pattern apparatus. Its only weakness is minor: a hardcoded Node version and light teaching content keep conciseness just below excellent.

Suggestions

Move the 'Node ≥ 20.19.0' version constraint into a prerequisites note or verify step rather than stating it inline, so the skill does not carry time-sensitive detail in the main flow.

Tighten the 'Entry vs project' paragraph to a one-line definition pair, since the distinction is the actionable part and the rationale can be trimmed.

Consider extracting the per-issue triage and anti-pattern tables into a reference file if the body grows, to keep SKILL.md a focused overview.

DimensionReasoningScore

Conciseness

The body is lean and largely free of padding, but the hardcoded version constraint 'Node ≥ 20.19.0' is time-sensitive detail outside a deprecated section, and the 'Entry vs project' explanation adds mild teaching beyond pure leanness, keeping it at 'mostly efficient'.

2 / 3

Actionability

Fully executable guidance throughout — concrete npm/npx commands, a copy-paste knip.json config, GitHub Actions YAML, and exact CLI flags like '--max-show-issues 5' and '--no-exit-code'.

3 / 3

Workflow Clarity

A clear seven-step sequence with validation checkpoints for the risky CI-gate step (baseline first so CI 'only fails on additions') plus a triage table for error recovery, satisfying the feedback-loop requirement.

3 / 3

Progressive Disclosure

No bundle files exist; external references are one level deep and clearly signaled in a References section, and the body is well organized into labeled sections (When to use, Steps, Anti-patterns, Limitations) rather than a monolithic wall.

3 / 3

Total

11

/

12

Passed

Description

100%

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

A strong, specific description that concretely names what Knip detects and gives explicit, natural trigger scenarios for when to use it. It clearly occupies a distinct niche and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'detect unused files, unused dependencies, unused exports, and unused class/enum members' — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (detect unused files/dependencies/exports/members) and when, opening with 'Use after a feature or route is deleted...', matching the score-3 anchor with an explicit trigger clause.

3 / 3

Trigger Term Quality

Trigger scenarios mirror natural developer speech ('after a feature or route is deleted and the project still compiles', 'package.json has accumulated dependencies nobody can account for') alongside natural terms like 'unused dependencies' and 'unused exports'.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Knip dead-code analysis in JS/TS), scoped to production code with framework-plugin-aware tests, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents