CtrlK
BlogDocsLog inGet started
Tessl Logo

dead-dependencies

Find and safely remove unused ("dead") npm dependencies in RedisInsight using a grep + leaf-check + build-gate recipe. Use when cleaning up dependencies, investigating whether a package is still used, removing a suspected leftover, or when the user mentions dead deps, unused dependencies, dependency cleanup, leftover packages, or "is this safe to remove". Complements the weekly vulnerability audit (`scripts/dependency-audit-report.mjs`), which only reports vulnerabilities.

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A well-structured, highly actionable skill body with an explicit validation gate and recovery loop. Slight conciseness and progressive-disclosure headroom keep it just short of perfect.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence with executable bash throughout, though the 'Why manual' rationale section is somewhat long and could be trimmed.

4 / 5

Actionability

Fully executable copy-paste grep commands, a leaf-check command, explicit gate commands, and a classification table mapping situations to concrete actions.

5 / 5

Workflow Clarity

A clear 5-step sequence with an explicit build-gate validation step and a feedback loop ('If anything goes red, it wasn't dead — restore it').

5 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with no nested references; a single self-contained file is appropriate here, with minor room for tighter overview/advanced separation.

4 / 5

Total

18

/

20

Passed

Description

95%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.

A strong description with explicit what/when guidance, comprehensive natural trigger terms, and a distinct niche. Minor specificity gaps keep it just below perfect on action coverage.

DimensionReasoningScore

Specificity

Names the domain and a concrete recipe method (grep + leaf-check + build-gate) plus the actions of finding and safely removing, with only minor coverage gaps.

4 / 5

Completeness

Explicitly states what it does (find and safely remove dead deps via a named recipe) and when to use it with concrete trigger phrases in a 'Use when...' clause.

5 / 5

Trigger Term Quality

Comprehensive natural terms and synonyms ('dead deps', 'unused dependencies', 'dependency cleanup', 'leftover packages') plus the quoted user phrase 'is this safe to remove'.

5 / 5

Distinctiveness Conflict Risk

Scoped to RedisInsight dead-deps and explicitly contrasted against the weekly vulnerability audit, giving it a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
redis/RedisInsight
Reviewed

Table of Contents

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.