CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/reachability-analyzer

Use whenever npm audit, OSV-Scanner or Snyk reports too many vulnerabilities and only the ones that matter should count. Finds dependencies the code never uses with knip or depcheck (JS), vulture (Python) or cargo-machete (Rust) and downranks their CVEs. EPSS and KEV: cve-exploitability-triage.

Quality

94%

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

92%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: executable commands per ecosystem, a complete annotation script, CI integration, an explicit validation feedback loop, and proper offloading of tool detail to a single well-signaled reference file. The only refinement available is deduplicating tool links and caveats that currently appear in two places.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (no re-explanation of how scanners or pip work), but the four GitHub tool links appear both inline and again in References, and the vulture --min-confidence, depcheck-archived, and --with-metadata caveats each appear twice (steps/limitations plus the anti-patterns table). Efficient with minor trimming opportunities, matching the 4 anchor rather than 5.

4 / 5

Actionability

Copy-paste-ready commands for all three ecosystems, a complete executable Python cross-reference script, a CI YAML snippet, and a worked example citing a real CVE (CVE-2022-31129, CVSS 7.5). Fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with an explicit validation checkpoint ("assert unused-deps.txt is non-empty and every finding ... carries a populated reachable field") and a feedback loop that names the likely failure cause and prescribes re-running and re-annotating — exactly the validate→fix→retry pattern the rubric rewards for batch operations.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview; per-tool detail (config, flags, exit codes, suppression) is correctly split into the single one-level-deep references/dead-dependency-tools.md (verified to exist, 148 lines), clearly signaled both at step 2 and in a descriptive References section. No nesting, easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%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 high-quality description that states concrete capabilities with named tools per ecosystem, opens with an explicit 'Use whenever' trigger naming the exact scanners users run, and even routes the neighboring EPSS/KEV use case to a different skill. The only gap is a few missing natural synonyms (SCA, triage, prioritization) beyond the tool names.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named per-ecosystem tools — "Finds dependencies the code never uses with knip or depcheck (JS), vulture (Python) or cargo-machete (Rust) and downranks their CVEs" — in third-person voice, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both: an unconditional trigger clause ("Use whenever npm audit, OSV-Scanner or Snyk reports too many vulnerabilities and only the ones that matter should count") and a concrete what (find unused dependencies per ecosystem and downrank their CVEs).

5 / 5

Trigger Term Quality

Strong natural terms users say during triage ("npm audit, OSV-Scanner or Snyk reports too many vulnerabilities", "CVEs", "dependencies"), but common synonyms like "SCA", "triage", or "dependency scanning" are absent. Good coverage with a few natural terms missing, which fits the 4 anchor better than 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (SCA prioritization via dead-dependency detection) with tool-specific triggers, and it explicitly disambiguates the adjacent skill: "EPSS and KEV: cve-exploitability-triage". 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page