CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codebase-cleanup-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

68%

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/codebase-cleanup-deps-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 organized with useful scope boundaries ("Do not use this skill when") and a sensible output format, but it operates at a purely abstract level: no tools, commands, or concrete steps anywhere, and the single reference that promised the details points to a file missing from the bundle. Redundant restatement of the description in the role, Use-when, and Context sections wastes tokens.

Suggestions

Replace abstract instructions with concrete, per-ecosystem commands (e.g., `npm audit --json`, `pip-audit -r requirements.txt`, `osv-scanner .`, `cargo audit`) so the scans and upgrade proposals are executable without external files.

Add explicit validation checkpoints to the workflow, e.g., re-run the vulnerability scan after proposed upgrades and confirm the project builds and its tests pass in staging before recommending rollout.

Either include `resources/implementation-playbook.md` in the bundle or remove the dangling reference (it is cited in both Instructions and Resources but the file does not exist); also drop the Context and Requirements sections, which merely restate the frontmatter description.

DimensionReasoningScore

Conciseness

The body is short and avoids explaining concepts Claude already knows, but the purpose statement is repeated roughly three times (the role paragraph "Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages...", the "Use this skill when" section, and "The user needs comprehensive dependency analysis..." in Context), and "Take the requirements, target, and scope from the user's request" is vacuous. Not 2 because there is no concept-explanation padding and each section is only a few lines; not 4 because the Context and Requirements sections add almost nothing beyond the frontmatter description.

3 / 5

Actionability

Instructions are high-level hints — "Inventory direct and transitive dependencies", "Run vulnerability and license scans", "Prioritize fixes by severity and exposure" — with no tool names, commands, or examples (e.g., npm audit, pip-audit, osv-scanner, cargo audit), which matches "minimal concrete guidance; high-level hints but missing the specific steps to execute". The one pointer to concrete detail ("open resources/implementation-playbook.md") targets a file that does not exist in the bundle, so the deferral provides no executable guidance.

2 / 5

Workflow Clarity

A rough sequence is present (inventory → scan → prioritize → propose upgrades) but checkpoints are mostly missing or implicit; the only verification note is "Verify upgrades in staging before production rollout" in Safety. Since proposing dependency upgrades is a batch operation on manifests/lockfiles and validation beyond the staging note is absent, workflow clarity is capped at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

Section structure is good and the single reference is clearly signaled in two places (Instructions and Resources), one level deep. However, scoring against the actual bundle: the referenced path "resources/implementation-playbook.md" does not exist — there is no resources/, references/, scripts/, or assets/ directory — so navigation breaks at the exact point where the skill defers all detailed workflows. Not 4 because a dangling reference is more than a minor organization gap; not 2 because the body itself is well organized and not monolithic.

3 / 5

Total

11

/

20

Passed

Description

78%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: concrete, third-person, with an explicit "Use when" trigger clause and a well-carved niche in dependency security auditing. The main gaps are missing ecosystem-specific trigger terms and a when-clause that could enumerate more concrete user-mention phrases.

DimensionReasoningScore

Specificity

Lists several concrete actions — "known vulnerabilities, licensing issues, outdated packages, and supply chain risk" plus "actionable remediation strategies" — but stops short of comprehensive coverage (no report generation, tooling, or upgrade-execution specifics). Not 5 because "provide actionable remediation strategies" is somewhat generic; not 3 because more than 1-2 concrete actions are explicitly named.

4 / 5

Completeness

Explicitly answers both: what ("Audit project dependencies for known vulnerabilities, licensing issues...") and when ("Use when reviewing or hardening the dependencies of a project"). Not 5 because the when-clause is narrower than the skill's stated scope and omits concrete trigger phrases like "vulnerable packages" or "CVEs"; the "Use when" clause is present so the completeness cap of 3 does not apply.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "dependencies", "vulnerabilities", "licensing", "outdated packages", "supply chain risk", "reviewing", "hardening" — phrases users would plausibly say. Not 5 because common variations are missing (e.g., "CVEs", "security scan", ecosystem terms like npm/pip/cargo, or manifest names like package.json/lockfile).

4 / 5

Distinctiveness Conflict Risk

Clear niche — dependency auditing with triggers ("vulnerabilities", "licensing", "supply chain risk", "dependencies of a project") that would not naturally fire a general code-review or document skill. Third-person imperative voice is used correctly; minimal conflict risk with closely related security skills since the scope is explicitly dependency-scoped.

5 / 5

Total

17

/

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/codebase-cleanup-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.