CtrlK
BlogDocsLog inGet started
Tessl Logo

secure-dependency-health-check

Helps choose secure, healthy open-source packages by evaluating vulnerability status, maintenance health, popularity, community, and security posture. Use this skill when: - Agent needs to import a new dependency - User asks "which package should I use for X?" - User wants to compare packages (A vs B) - User asks "is this package safe?" - User asks for a "secure alternative" to a package - User mentions "dependency health", "package chooser", or "package security"

68

Quality

83%

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

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

Well-structured and actionable body with clear sequencing and concrete tool guidance, but it underutilizes the existing reference file by not linking to it from SKILL.md. Adding explicit pointers to the reference would lift progressive disclosure.

Suggestions

Add a one-level reference pointer (e.g. 'See [package-evaluation-criteria.md](references/package-evaluation-criteria.md) for detailed rating thresholds and the decision framework') so the body navigates to the existing bundle file.

Add an explicit validate->fix->retry loop for the recommendation step (e.g. re-run health check after pinning a version to confirm no new advisories) to strengthen workflow checkpoints.

Trim the templated comparison-table and alternative-scenario blocks to the essential rows/scenarios to tighten conciseness.

DimensionReasoningScore

Conciseness

Efficiently structured into phases without over-explaining concepts Claude knows; minor verbosity in the templated comparison and alternative-scenario blocks that could be trimmed.

4 / 5

Actionability

Concrete tool name, ecosystem list, exact response fields, disqualifier thresholds (e.g. 'No releases in 3+ years'), and version-pinning guidance; the comparison template is fill-in rather than runnable, appropriate for an instruction skill.

4 / 5

Workflow Clarity

Clear four-phase sequence with sub-steps and disqualifier checkpoints plus post-install scan validation; lacks an explicit validate->fix->retry loop on the recommendation itself, leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

A reference file exists (references/package-evaluation-criteria.md) but the body never links to or signals it, and detailed criteria/decision-framework content sits in the reference rather than being surfaced via clear one-level navigation.

3 / 5

Total

15

/

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 comprehensive natural trigger phrases and an explicit 'Use when' clause covering both what and when. Minor room to sharpen the action list toward fully comprehensive concrete actions.

DimensionReasoningScore

Specificity

Names the domain and enumerates five concrete evaluation facets (vulnerability status, maintenance health, popularity, community, security posture); not quite comprehensive enough for a 5 but clearly above midpoint.

4 / 5

Completeness

Explicitly answers both what (choose secure healthy packages by evaluating five facets) and when, via a concrete 'Use this skill when' clause with six trigger conditions.

5 / 5

Trigger Term Quality

Covers natural phrases users actually say including synonyms ('which package should I use for X?', 'is this package safe?', 'secure alternative', 'dependency health', 'package chooser', 'package security').

5 / 5

Distinctiveness Conflict Risk

Clear niche of secure/healthy package selection with distinct, specific triggers and minimal overlap risk with unrelated skills.

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
snyk/studio-recipes
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.