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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/framework-migration-deps-upgrade/SKILL.md

The canonical home for this skill is framework-migration-deps-upgrade in rmyndharis/antigravity-skills

Quality

Content

36%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 organized into clear sections but offers mostly generic, non-executable guidance with no real sequenced workflow or validation checkpoints, and its single detailed reference is a broken path. It reads as a template skeleton rather than a skill that tells Claude exactly what to do.

Suggestions

Replace the generic Instructions bullets with concrete, executable steps (specific commands for assessing outdated deps, running tests, and rolling back) or provide the missing implementation-playbook.md.

Add a sequenced workflow with explicit validation checkpoints (e.g., run test suite, verify compatibility, confirm rollback path) for the upgrade process.

Remove the redundant Context paragraph that restates the description, and fix or create the referenced resources file so progressive disclosure actually resolves.

Dimension	Reasoning	Score
Conciseness	Mostly brief, but the Context section restates the description and the Instructions bullets ('Clarify goals...', 'Apply relevant best practices...', 'Provide actionable steps and verification') are generic filler Claude already knows and could be tightened.	3 / 5
Actionability	Guidance is high-level and abstract with no concrete commands, code, or specific steps; the only detailed reference (resources/implementation-playbook.md) does not exist in the bundle, leaving minimal executable guidance.	2 / 5
Workflow Clarity	Instructions are a generic three-bullet list and the Output Format is a deliverable list rather than a sequenced procedure, with no explicit validation checkpoints or feedback loops.	2 / 5
Progressive Disclosure	Sections are organized and a one-level-deep reference is signaled, but the referenced resources/implementation-playbook.md is absent from the bundle, undermining the otherwise reasonable structure.	3 / 5
	Total	10 / 20 Passed

Description

48%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 identifies a clear niche and lists several actions but uses second-person voice, omits an explicit 'Use when' trigger, and lacks natural user phrasing. These issues keep it near the middle of the scale rather than at the top.

Suggestions

Rewrite in third person (e.g., 'Plans and executes safe, incremental dependency upgrades...') to avoid the second-person specificity penalty.

Add an explicit 'Use when...' clause with natural trigger phrases such as 'upgrade dependencies', 'bump packages', or 'fix outdated dependencies'.

Include concrete operations and synonyms/file extensions (e.g., package managers, lockfiles) to raise both specificity and trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and a few process actions ('Plan and execute dependency updates', 'minimal risk, proper testing, and clear migration paths'), but the actions are generic process steps rather than concrete operations; additionally the second-person voice ('You are...') triggers a one-point specificity penalty.	2 / 5
Completeness	It clearly states what the skill does but contains no 'Use when...' trigger clause, so completeness is capped at 3 per the rubric's missing-trigger guidance and matches the 'clear what, missing when' anchor.	3 / 5
Trigger Term Quality	Relevant keywords ('dependency', 'upgrades', 'dependencies', 'migration') are present but common natural variations users say ('upgrade my packages', 'bump deps', 'outdated dependencies', 'npm update') are missing.	3 / 5
Distinctiveness Conflict Risk	The dependency-upgrade niche is mostly distinct with only minor overlap risk against closely related versioning or migration skills.	4 / 5
	Total	12 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/framework-migration-deps-upgrade/SKILL.md
Commit: 57c135b

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