CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-deps

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

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 dense, highly executable runbook whose sequencing, validation gates, and degraded-network handling are exemplary. It falls slightly short of top marks on token efficiency (occasional rhetorical padding), actionability (a few steps are direction rather than commands), and disclosure (a single long file with no internal split).

Suggestions

Trim the rhetorical framing (e.g. "a guess dressed as a fact", "which is the run this report most often describes") to pure instruction — the rules they dramatize can be stated as one-line imperatives.

Give executable forms for the two procedural steps: a concrete WebFetch/jq recipe for extracting dist-tags.latest and the relevant time entries, and the ordered changelog-lookup as commands or URLs rather than prose.

Move the Step 5b skill-pin verification details (SHA-safety check, installer invocation, check scripts) into a short reference file or lean harder on the cited wiki section, letting SKILL.md carry only the decision rules.

DimensionReasoningScore

Conciseness

The body is command-first and assumes competence — jq/bash pipelines are given without explanation — and its rationale sentences state repo-specific rules Claude cannot know (e.g. the peerDependencies-as-contract rule). A few rhetorical flourishes ("a guess dressed as a fact", "which is the run this report most often describes") could be trimmed, which keeps it at efficient-with-minor-excess rather than every-token-earns-its-place.

4 / 5

Actionability

Most steps ship copy-paste artifacts: the verbatim DEPS-REVIEW.md heredoc, the find/jq collection pipeline, the uniq -d drift detector, bun outdated, gh api with --jq, and the installer command. Minor gaps remain — the registry fetch and changelog reading are described procedurally rather than scripted, and Step 7 delegates its commands to an external file — so it is mostly-executable rather than fully so.

4 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced, prerequisites are probed once up front and gate the run, guardrails are explicit ("Never write a version ... you did not fetch"), and the destructive apply is confirmation-gated and validated with typecheck, lockfile evidence, an audit-as-stop rule, and a final structural check that must print 4. Explicit checkpoints with feedback loops across a batch operation match the top anchor.

5 / 5

Progressive Disclosure

Sections are well organized and the skill-pin procedure is delegated to a clearly signaled, one-level-deep authority (wiki/conventions/agent-tooling.md §Third-party skills) instead of being duplicated. However, the ~150-line body keeps everything inline with no split of its own — the under-50-line simple-skill exception does not apply — so structure is good with minor organization gaps rather than a clear overview-plus-references layout.

4 / 5

Total

17

/

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 strong, third-person description that states both an explicit use-when trigger and a comprehensive, concrete action list for a well-defined niche. The only gap is a handful of natural synonyms (e.g. "outdated", "bump versions") that users might say instead of "version drift" or "upgrades".

DimensionReasoningScore

Specificity

The description lists five concrete, distinct actions covering the full pipeline — "Finds the packages whose declared ranges disagree", "checks the registry for newer versions", "classifies each upgrade against the waiting-period rules", "reads the changelogs and upstream diffs", "reports the package.json and skill-pin changes to make" — matching the comprehensive-coverage anchor; it is not the level below because no part of the job is left out.

5 / 5

Completeness

It opens with an explicit trigger clause — "Use when auditing the monorepo's dependencies — ... — for version drift between workspaces and for upgrades available on npm or upstream" — and pairs it with a concrete what-list, clearly answering both questions as the top anchor requires. Not the level below, because the when is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Natural domain phrases are present ("auditing the monorepo's dependencies", "version drift", "upgrades available on npm", "skills-lock.json", "changelogs") but common user phrasings like "outdated packages" or "update/bump dependencies" are missing. This fits the good-coverage-with-a-few-missing-terms anchor rather than the comprehensive-synonyms anchor, and is well above the generic-keyword anchors.

4 / 5

Distinctiveness Conflict Risk

Terms like "workspace package.json", "skills-lock.json", "skill-pin changes" and "waiting-period rules" carve a clear niche with distinct triggers that no generic dependency or docs skill would fire on. Minimal conflict risk, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

.claude/skills/review-deps/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.