framework-migration-deps-upgrade

You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration pa

Quality

42%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/framework-migration-deps-upgrade/SKILL.md

Quality

Content

35%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is organized and concise but offers only vague, generic instruction with no executable commands or concrete tooling, and it points to a referenced file that is not present in the bundle, which weakens both actionability and disclosure.

Suggestions

Replace generic Instructions with concrete, executable guidance, e.g. specific commands like `npm outdated`, `pip list --outdated`, `npm audit`, lockfile regeneration, and a representative upgrade-before/after diff.

Add explicit validation/feedback-loop checkpoints (run test suite -> if failures, revert via lockfile/commit -> re-test) so the upgrade workflow scores above 2.

Either create `resources/implementation-playbook.md` so the referenced file exists, or remove the dangling reference; ensure the path matches the actual bundle directory (`references/`).

Dimension	Reasoning	Score
Conciseness	Mostly short and sectioned, but it restates the description verbatim and pads the Instructions with generic boilerplate ('Apply relevant best practices and validate outcomes') that could be tightened; it avoids over-explaining concepts Claude already knows.	2 / 3
Actionability	The Instructions ('Clarify goals...', 'Apply relevant best practices...', 'Provide actionable steps and verification') are abstract and describe rather than instruct, with no concrete commands, tooling, or code, matching the 'vague or abstract; no concrete code/commands' anchor.	1 / 3
Workflow Clarity	The Output Format gives a loose ordering (overview -> priority matrix -> guides -> tests -> rollback) but there is no validation checkpoint or feedback loop, and the rubric caps risky batch operations like dependency upgrades at 2 when validation is missing.	2 / 3
Progressive Disclosure	The body is short and sectioned and signals a reference to `resources/implementation-playbook.md` in two places, but no bundle directory exists (references/, scripts/, assets/ are all empty), so the referenced file is a broken/dangling pointer.	2 / 3
	Total	7 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 conveys a clear domain and several concrete actions but is truncated mid-sentence ('migration pa'), uses penalized second-person voice, and omits any explicit trigger clause, leaving every dimension capped at the middle level.

Suggestions

Complete the truncated sentence and add an explicit trigger, e.g. 'Use when the user asks to upgrade or update project dependencies, bump package versions, or resolve dependency conflicts.'

Rewrite in third person ('Plans and executes incremental dependency upgrades...') instead of 'You are a dependency management expert' to avoid the specificity penalty.

Add natural trigger variations users actually say, such as 'npm update', 'pip install --upgrade', 'outdated packages', or 'lockfile'.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('safe, incremental upgrades', 'Plan and execute dependency updates with minimal risk, proper testing') which would merit a 3, but it uses second-person voice ('You are a dependency management expert') which the rubric penalizes by reducing specificity by one.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' trigger or equivalent explicit guidance on when to invoke it, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes relevant natural terms like 'dependency updates' and 'upgrades', but misses common variations a user would actually say (e.g. 'update packages', 'npm/pip outdated', 'version bumps', 'lockfile').	2 / 3
Distinctiveness Conflict Risk	The dependency-upgrade niche is somewhat specific but 'Plan and execute dependency updates' is broad enough to overlap with general coding or package-management skills.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/framework-migration-deps-upgrade/SKILL.md
Commit: e63f7dd

Reviewed: 13 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.