dependency-update

Read release notes/changelogs, update a defined dependency scope, handle breaking changes, and verify. Explicit-only; no broad update-everything by inference.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crates/tui/assets/skills/dependency-update/SKILL.md

Quality

Content

65%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 exceptionally concise and well-structured, but the workflow is too abstract to be fully actionable and lacks an explicit feedback loop for batch dependency updates. Adding concrete commands and a retry-on-failure step would lift the weakest dimensions.

Suggestions

Add concrete executable detail per step, e.g. how to inspect current versions ('cat package.json' / 'npm outdated') and how to apply updates ('npm install pkg@version').

Insert an explicit validation feedback loop: after 'Verify', add 'If tests/build fail, review breaking changes, fix, and re-verify before proceeding.'

Optionally reference where release notes/changelogs are typically found (e.g. GitHub Releases, CHANGELOG.md) to make step 2 actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of concepts Claude already knows; every section (Invocation, Non-goals, Workflow) earns its place.	5 / 5
Actionability	Steps like 'Read release notes/changelogs', 'Apply updates and fix breakages', and 'Verify with the project's test/build gates' are high-level hints without specific commands, file paths, or examples of how to execute them.	2 / 5
Workflow Clarity	A clear four-step sequence with a verify step is present, but there is no feedback loop (verify -> fix -> retry) for this batch operation, so per the rubric workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	This is a simple, under-50-line single-purpose skill with well-organized sections and no need for external references or bundle files, qualifying for the simple-skill exception.	5 / 5
	Total	15 / 20 Passed

Description

71%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 specific and concise with several concrete actions and a clear niche, but it lacks an explicit 'when to use' trigger clause, capping completeness. Adding a 'Use when...' sentence with synonyms like 'upgrade' and 'bump' would raise the weaker dimensions.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to update, upgrade, or bump dependencies or handle breaking changes from a new release.'

Include natural synonyms users say — 'upgrade', 'bump version', 'package' — to broaden trigger term coverage.

Clarify the dependency scope (e.g. language ecosystem or manifest type) to further reduce overlap with general maintenance skills.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'Read release notes/changelogs', 'update a defined dependency scope', 'handle breaking changes', and 'verify' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms like 'release notes/changelogs', 'breaking changes', and 'dependency', but misses common synonyms users say such as 'upgrade', 'bump', 'package', or 'version'.	4 / 5
Distinctiveness Conflict Risk	The dependency-update niche with 'defined dependency scope' and 'breaking changes' is mostly distinct, with only minor overlap risk against general coding/maintenance skills.	4 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Hmbown/CodeWhale
Path: crates/tui/assets/skills/dependency-update/SKILL.md
Commit: 8ae401b

Reviewed: 2 days 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.