review-deps

Use when auditing the monorepo's dependencies — every workspace package.json — for version drift between workspaces and for upgrades available on npm. Finds the packages whose declared ranges disagree, checks the registry for newer versions, classifies each upgrade against the waiting-period rules, reads the changelogs of the ready ones, and reports the package.json changes to make.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

96%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 tight, fully executable multi-step workflow with strong validation feedback loops and a resilience-to-network-failure design. It is lean and actionable; the only soft spot is progressive disclosure, where the long inline body could offload some heuristics to a reference file.

Suggestions

Move the Step 5 changelog-source heuristics (CHANGELOG.md/RELEASES.md/GitHub releases/npm page fallback order) into a references/changelog-sources.md and link to it, shortening the main body.

Consider extracting the drift-detection three-rules block into a reference so Step 2 stays a concise procedure.

Dimension	Reasoning	Score
Conciseness	Lean, instruction-dense body with no explanation of concepts Claude already knows; the prose present (peerDependencies as a compatibility contract, overrides as a floor, the alignment target) is genuine non-obvious domain rule, not padding.	5 / 5
Actionability	Fully executable: concrete find/jq pipelines, `bun outdated --filter '*'`, registry WebFetch with the exact fields to take, a verbatim report skeleton, and a classification table with numeric thresholds — copy-paste ready for the common cases.	5 / 5
Workflow Clarity	Steps 0–7 are clearly sequenced with explicit validation checkpoints: a prerequisite probe before starting, a verbatim skeleton written first, a final `grep -c` check (both must print 4), `bun install --frozen-lockfile` verification, and a `bun audit` stop condition.	5 / 5
Progressive Disclosure	Well-organized into clearly headed steps with content appropriately inline (the report template and classification table belong here), and no bundle files exist that should be referenced; minor gap is the length (~130 lines) with no external reference split for the changelog-reading heuristics.	4 / 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 precise, third-person description that pairs a concrete action chain with an explicit 'Use when' trigger covering both version drift and npm upgrades. It is distinct and comprehensive, with only minor synonym gaps in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Finds the packages whose declared ranges disagree, checks the registry for newer versions, classifies each upgrade against the waiting-period rules, reads the changelogs of the ready ones, and reports the package.json changes to make' — comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Explicitly answers both 'what' (the chain of finds/checks/classifies/reads/reports) and 'when' ('Use when auditing the monorepo's dependencies ... for version drift ... and for upgrades available on npm') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger phrasing ('auditing the monorepo's dependencies', 'version drift', 'upgrades available on npm'), but a few common synonyms a user might say ('outdated', 'bump', 'update dependencies') are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (monorepo workspace package.json drift + npm upgrade classification with waiting-period rules) unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: xchromo/osn
Path: .claude/skills/review-deps/SKILL.md
Commit: 5438649

Reviewed: ~11 hours ago

Table of Contents

Discovery Implementation Validation

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.