CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dep-radar

Load to run or tune a dependency sweep.

Quality

64%

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/dep-radar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 an exceptionally lean, information-dense policy engine — the operating-policy and playbook tables are near-flawless token economy with concrete commands and verification steps. Its credibility collapses on delivery, though: the entire sweep procedure it repeatedly defers to lives in workflows/sweep.md, which is missing from the bundle, leaving the core workflow unreachable and the overview-to-detail structure non-functional.

Suggestions

Ship the missing workflows/sweep.md (or inline the phase-by-phase procedure) — both references to it, including the '§ Phase 4' anchor link, currently point to a file that does not exist in the bundle.

Integrate the Verify column's checkpoints into an explicit ordered workflow with feedback loops, e.g., 'upgrade → run verify step → on failure, fix fallout in the same PR and re-verify → only then open the per-surface PR', so validation is sequenced rather than a parallel table column.

Specify run-level orchestration in the body — surface ordering, merge-order handling for migration-bearing bumps, and what a 'dated report' must contain — since the guardrails flag these hazards but defer all handling to the absent workflow file.

DimensionReasoningScore

Conciseness

The body is dense operational rule-setting with zero concept explanation — it names `pnpm -r outdated`, `cargo update --dry-run`, and `cargo audit` without preamble and never explains what dependencies or registries are, matching anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place'). Every table row and bullet carries a substantive constraint (e.g., 'never a third party, never hand-computed from a local download alone'), with no dated/version-specific content that would need an old-patterns section.

5 / 5

Actionability

Concrete guidance is present — exact check commands (`pnpm -r outdated`, `pnpm audit`), per-surface verification ('Pin unit tests + a live download smoke on the host platform'), and precise tier rules — but the primary task's executable procedure is the instruction "follow [workflows/sweep.md](workflows/sweep.md)", and that file does not exist in the bundle, so the key execution details are unreachable. This matches anchor 3 ('Some concrete guidance but incomplete... missing key details') rather than anchor 4, whose gaps are only minor.

3 / 5

Workflow Clarity

A sequence is named ("inventory → detect → research → classify → upgrade-with-fixes → report the owner tier") and per-surface checkpoints exist in the Verify column, but the two are never integrated into ordered steps with feedback loops — what happens inside each phase and when a failed verification is retried versus reported lives only in the missing workflows/sweep.md. This is anchor 3 ('Steps listed but validation gaps; sequence present but checkpoints missing or implicit'), not anchor 4, because the phase-level sequencing gaps are structural, not minor.

3 / 5

Progressive Disclosure

The overview/referenced-file split is well designed on paper — a 47-line SKILL.md with a clearly signaled, one-level-deep pointer ("When running a dependency sweep, follow [workflows/sweep.md](workflows/sweep.md)") — but scoring against the actual bundle, workflows/sweep.md is absent and no references/, scripts/, or assets/ directories exist, so the single disclosure path is a dead end. This lands at anchor 2: the effective structure is broken even though the in-file organization itself is not the problem, and it avoids anchor 1 only because the SKILL.md body itself remains navigable.

2 / 5

Total

13

/

20

Passed

Description

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

The description is grammatically clean and honest but skeletal: at eight words it names the domain and two generic actions while offloading all substance to a separate summary field the description rubric does not credit. It reads as a load-trigger fragment rather than a self-contained what+when statement.

Suggestions

State what the sweep actually does inside the description itself (e.g., 'checks every pinned dependency against upstream and lands upgrades with their fallout in one PR per surface') instead of the circular 'run... a dependency sweep'.

Add natural trigger phrases users would say — 'outdated dependencies', 'bump versions', 'upgrade deps/packages' — since only 'dependency' currently functions as a trigger term.

Add an explicit 'when' clause (e.g., 'Use when asked to update, audit, or upgrade pinned dependencies') so completeness does not rest on the terse 'Load to' phrasing.

DimensionReasoningScore

Specificity

"run or tune a dependency sweep" names the domain and two actions, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' (like "Processes PDF files and extracts content"). It does not reach 4 because the verbs "run" and "tune" are generic and the description never says what a sweep actually does, and it clears 2 because two distinct actions are explicitly stated rather than one minimal generic action.

3 / 5

Completeness

The single clause "Load to run or tune a dependency sweep" does double duty: the 'what' is circular (a dependency sweep runs... a dependency sweep, with no statement of what it does — the check-upstream/land-upgrades detail lives only in the separate summary field) and the 'when' is a terse "Load to" with no concrete trigger phrases. This fits anchor 3 ('Has a clear what but when is missing or only weakly implied') better than anchor 4, whose example pairs a substantive 'what' with an explicit "Use when..." clause.

3 / 5

Trigger Term Quality

"dependency" is a relevant keyword users would naturally say, but "sweep" is this skill's own jargon rather than a user phrase, and common variations like "outdated", "upgrade", "update", "bump", "deps", or "packages" are absent — matching anchor 3 ('Some relevant keywords but missing common variations or synonyms'). It is above anchor 2 because "dependency" is a specific domain term, not a generic keyword like "files".

3 / 5

Distinctiveness Conflict Risk

"dependency sweep" carves out a mostly distinct niche (pinned-version inventory, upstream checks, upgrade landing) with only minor overlap risk against closely related release/version-bump skills, matching anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'). It falls short of anchor 5 because the description offers only one distinguishing trigger term rather than 'distinct triggers' in the plural.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

skills/dep-radar/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.