CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

l-update-deps

Update a single dependency by reading its full changelog and assessing impact. Safe updates are applied directly, major updates are flagged for design review. Use when updating packages.

Quality

79%

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 ./.claude/skills/l-update-deps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable six-step workflow with concrete commands, decision branches, and test-based validation. It loses points for a couple of non-executable placeholder snippets, some minor redundancy and emphasis padding, and a shallow failure-recovery loop.

Suggestions

Replace the placeholder jq filter and the empty 'Find all imports' bash block with executable equivalents (e.g., a concrete `gh api` jq expression and an actual `rg 'from ["'']package'` example).

Remove the duplicate explanation of the '(dev)' marker and trim emphasis sentences ('This is the most important step', 'Do not skim') since the surrounding instructions already convey them.

Deepen the step-5 failure loop: instruct re-running the affected package tests after each fix and stopping to report if failures persist.

DimensionReasoningScore

Conciseness

The body is mostly lean commands and terse decision rules, but has minor removable padding: the '(dev)' marker is explained twice (lines 34 and 72) and emphasis lines like 'This is the most important step' and 'Do not skim' add tokens without adding information.

4 / 5

Actionability

Provides concrete executable pnpm/gh/npm commands for most steps, but two spots are incomplete: the release-filter jq snippet uses non-executable placeholder syntax (test("v?{from}|v?{to}|...")) and step 4 opens with an empty bash block containing only a comment before deferring vaguely to 'Use Grep'.

4 / 5

Workflow Clarity

The six steps are clearly sequenced with explicit semver/dependency-type decision branches, an early checkpoint ('If already up to date, say so and stop'), and test-based validation with a feedback loop ('If tests fail, investigate and fix'). The recovery loop is shallow — no fix-and-re-run detail or checklist — so it stops short of a 5.

4 / 5

Progressive Disclosure

A single well-sectioned file with no bundle files and a cohesive one-workflow scope; nothing clearly demands extraction into references. The ~175-line body and the long inline example listing (lines 40-66) keep it at 'good structure' rather than a clear overview with well-signaled references.

4 / 5

Total

16

/

20

Passed

Description

75%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 solid description that states concrete capabilities in third person and includes an explicit 'Use when' trigger. It falls just short of top marks because the trigger guidance is thin (single generic phrase, no synonyms like 'upgrade'/'bump') and the capability list omits later workflow steps.

Suggestions

Broaden the trigger clause to include natural variations, e.g. 'Use when updating, upgrading, or bumping a package or dependency.'

Mention the listing mode ('lists outdated packages when none is specified') so the what-clause covers the skill's full behavior.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Update a single dependency by reading its full changelog and assessing impact', 'Safe updates are applied directly, major updates are flagged for design review') but omits parts of the workflow (listing outdated packages, testing, committing), so coverage has minor gaps.

4 / 5

Completeness

Clearly answers 'what' with the full update-and-assess workflow and has an explicit 'Use when updating packages' trigger, but the 'when' clause is a single thin trigger with no concrete phrase variations.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('update', 'dependency', 'packages', 'major updates') but misses common synonyms like 'upgrade' and 'bump', so keyword coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The changelog-driven, safety-graded update policy is a distinct niche, though the generic trigger 'Use when updating packages' leaves minor overlap risk with general package-management requests.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

lowdefy/lowdefy

Path

.claude/skills/l-update-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.