CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dependency-management-deps-audit

Audit project dependencies for known vulnerabilities, licensing issues, outdated packages, and supply chain risk, and provide actionable remediation strategies. Use when reviewing or hardening the dependencies of a project.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/dependency-management-deps-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well-structured and token-efficient but operationally hollow: it tells Claude what to do at a managerial level without a single executable command or tool name, and its only path to concrete detail is a reference to a playbook file that is missing from the bundle. Fixing the broken reference and grounding the instructions in real tooling would lift the two weakest dimensions substantially.

Suggestions

Ground the instructions in executable specifics: name and show actual commands such as 'npm audit --json', 'pip-audit', or 'osv-scanner' for the scan step, so 'Run vulnerability and license scans' becomes copy-paste-ready guidance.

Add explicit validation checkpoints and a feedback loop, e.g. verify scan output parsed correctly, test upgrades in a staging branch, and re-run scans after upgrading to confirm vulnerabilities are resolved — currently only the Safety section's staging note gestures at this.

Repair the progressive-disclosure path: resources/implementation-playbook.md is referenced twice but does not exist in the bundle — either ship the playbook with the detailed tooling/templates it promises or remove the dangling pointer and inline the essential workflow.

DimensionReasoningScore

Conciseness

The body is short and mostly lean bullet-style instructions with no explanation of concepts Claude already knows, but the 'Context' section merely restates the frontmatter description and the 'Requirements' section ("Take the requirements, target, and scope from the user's request") is boilerplate filler — minor padding that keeps it below anchor 5's every-token-earns-its-place standard.

4 / 5

Actionability

Instructions are high-level directives ("Inventory direct and transitive dependencies", "Run vulnerability and license scans", "Propose upgrades with compatibility notes") with no tool names, commands, or code — 'run scans' without naming npm audit, pip-audit, or osv-scanner is a high-level hint missing the specific steps to execute, matching anchor 2.

2 / 5

Workflow Clarity

The five instruction bullets form a recognizable sequence (inventory, scan, prioritize, propose, optionally consult playbook), and the Safety section adds one checkpoint ("Verify upgrades in staging before production rollout"), but validation is otherwise absent or implicit — no step for verifying scan results, handling failed upgrades, or re-testing — fitting anchor 3's 'sequence present but checkpoints missing'.

3 / 5

Progressive Disclosure

Sections are clearly organized and the reference is well-signaled (dedicated Resources section plus an in-flow pointer), but the referenced file resources/implementation-playbook.md does not exist anywhere in the bundle — the single disclosure hop is broken, so navigation fails exactly where detail is supposed to live; this sits between anchor 3's weak references and anchor 2's structural failures.

3 / 5

Total

12

/

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.

A well-crafted description in third person that explicitly covers both capabilities and use conditions with domain-specific vocabulary. It consistently sits at the 'good but not exemplary' anchor: the 'when' clause and keyword set could be expanded with concrete trigger variants and manifest file names to reach the top anchor.

DimensionReasoningScore

Specificity

Lists several specific audit targets ("known vulnerabilities, licensing issues, outdated packages, and supply chain risk") plus remediation, but the distinct action verbs reduce to just 'audit' and 'provide remediation strategies' — short of anchor 5's density of multiple distinct concrete actions, yet well beyond anchor 3's 1-2 actions.

4 / 5

Completeness

Both 'what' (audit dependencies for vulnerabilities, licensing, outdated packages, supply chain risk; provide remediation) and an explicit 'when' ("Use when reviewing or hardening the dependencies of a project") are present; the 'when' clause offers a single phrasing rather than the enumerated concrete trigger variants of anchor 5, and 'reviewing' is somewhat generic.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("vulnerabilities", "licensing issues", "outdated packages", "supply chain risk", "dependencies") that users would plausibly say, but missing common synonyms and manifest triggers like package.json, requirements.txt, or 'npm audit' that anchor 5 expects.

4 / 5

Distinctiveness Conflict Risk

Dependency auditing is a clear, well-demarcated niche with domain-specific triggers (supply chain risk, licensing, outdated packages), but 'hardening' and 'reviewing' are broad terms with minor overlap risk against general security-review or code-review skills, so it is not the minimal-conflict niche of anchor 5.

4 / 5

Total

16

/

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.

Repository

rmyndharis/antigravity-skills

Path

skills/dependency-management-deps-audit/SKILL.md

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.