CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dep-radar

Load to run or tune a dependency sweep.

Quality

51%

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

Quality

Content

53%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-conceived: a terse generic engine with a rule-key contract table, per-surface playbooks with concrete upstream-check commands, and appropriate delegation of the detailed workflow to a separate file. However, that referenced file (workflows/sweep.md) is absent from the bundle, leaving the core sweep procedure — the skill's central content — inaccessible, and verification steps named but not executable. The policy framework is strong; the delivered bundle is incomplete.

Suggestions

Ship workflows/sweep.md in the bundle (or inline the sweep phases into SKILL.md) so the referenced core procedure actually resolves — every path cited in the body should exist.

Make the Verify column executable: give the actual commands (e.g. the typecheck/test invocations, the workflow-run check) instead of naming suites generically.

Trim the duplication between the Operating policy table's auto-with-fixes row and the Playbooks rows (majors-included, same-PR fallout handling) so each rule is stated once.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basic concepts are explained, and the tables pack contract details efficiently ("Rule keys are the contract; an inventory owner-rule cites them. Dropping or renaming a key changes the contract."). It is not 5 because the `auto-with-fixes` scope (majors included, fix fallout in the same PR) is stated in both the Operating policy table and again across several Playbooks rows, a redundancy that could be trimmed.

4 / 5

Actionability

Some commands are concrete ("pnpm -r outdated", "cargo update --dry-run", "cargo audit", "kendex report") but the core procedure is delegated to [workflows/sweep.md](workflows/sweep.md), which does not exist in the bundle, and the Verify column names checks ("Typecheck + tests", "Workflow run") without executable commands. This matches 'Some concrete guidance but incomplete; missing key details'; it is not 4 because the gap is not minor — the primary workflow cannot be executed from what is written.

3 / 5

Workflow Clarity

The sequence exists only as a named arrow chain ("inventory → detect → research → classify → upgrade-with-fixes → report the owner tier") with the actual step detail in the missing workflows/sweep.md, though checkpoints are partially present via the Verify column, test-suite gating for fork syncs, and "report only what actually failed, with error output". It is not 4 because a clear sequence with most checkpoints requires the steps themselves to be defined; as a batch operation touching many dependencies, the rubric also caps this dimension at 3 absent fully explicit validation.

3 / 5

Progressive Disclosure

The body correctly delegates its workflow to a clearly signaled one-level-deep reference, but the bundle contains no workflows/, references/, scripts/, or assets/ directories — the sole referenced path (workflows/sweep.md) is dangling, so navigation to the primary content fails entirely, and 'orch SKILL.md § Harness-Safe Shell' is likewise unverifiable. This matches 'Minimal structure' as delivered; it is not 3 because the problem is not unclear signaling but a broken reference chain that makes the skill's main content inaccessible.

2 / 5

Total

12

/

20

Passed

Description

28%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 extremely terse (nine words) and reads as internal shorthand rather than a discovery trigger. It names the domain but omits any 'Use when...' trigger guidance and any concrete characterization of the sweep's actions. Users asking to 'update' or 'upgrade dependencies' would likely not match this description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to update, upgrade, or audit dependencies, or mentions outdated packages.'

Enumerate 1-2 concrete actions so the 'what' is clear, e.g. 'Detects outdated dependencies, applies upgrades with fixes, and reports per-owner tiers.'

Include natural synonyms users actually say (update, upgrade, outdated, audit, patch) rather than only the internal term 'sweep'.

DimensionReasoningScore

Specificity

The description names the domain ("dependency sweep") but the actions are generic verbs — "Load to run or tune" — with no concrete characterization of what a sweep involves (detect, upgrade, fix fallout, report). This matches the anchor 'Names the domain but actions are minimal or generic' ("Processes PDF files"). It is not 3 because there is no second concrete action like 'extracts content' in the anchor example, and not 1 because the domain is explicitly named.

2 / 5

Completeness

The 'what' is vague ("run or tune a dependency sweep" does not say what a sweep does) and there is no 'when' clause at all — "Load to..." is a loading instruction, not trigger guidance. This matches 'Has a vague what and no when'; it cannot be 3 because a 3 requires a clear 'what', and the missing 'Use when...' clause alone would cap the score at 3.

2 / 5

Trigger Term Quality

The only real keyword is "dependency"; "sweep" is internal jargon users would rarely say, and natural phrases like "update dependencies", "upgrade packages", "outdated", or "audit" are absent. This matches 'One or two generic keywords; missing the natural phrases users say'. It is not 3 because the description lacks the common variations and synonyms that anchor requires.

2 / 5

Distinctiveness Conflict Risk

"Dependency sweep" carves out a recognizable niche with low wrong-skill trigger risk, but "dependency" is broad enough to overlap with generic dependency-update/audit skills. This matches 'Somewhat specific but could still overlap with similar skills'; it is not 4 because the terse, jargon-heavy phrasing gives no distinguishing trigger vocabulary.

3 / 5

Total

9

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/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.