hardhat-deploy-migration
Comprehensive guide for migrating projects from hardhat-deploy v1 to v2, including dependency updates, configuration restructuring, deploy script conversion, test updates, and troubleshooting
74
61%
Does it follow best practices?
Impact
100%
5.26xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/hardhat-deploy-migration/SKILL.mdQuality
Discovery
67%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 does well at specifying concrete migration actions and occupying a clear, distinct niche around hardhat-deploy v1-to-v2 migration. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding natural trigger terms users might say would also improve discoverability.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about upgrading or migrating hardhat-deploy from v1 to v2, or encounters breaking changes after updating hardhat-deploy.'
Include additional natural trigger terms like 'upgrade hardhat-deploy', 'hardhat deploy plugin migration', 'hardhat-deploy breaking changes', or 'solidity deploy scripts update'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'dependency updates, configuration restructuring, deploy script conversion, test updates, and troubleshooting'. These are clear, actionable migration steps. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (migrating hardhat-deploy v1 to v2 with specific steps), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'hardhat-deploy', 'v1 to v2', 'migrating', 'deploy script', but misses common user variations like 'upgrade hardhat-deploy', 'hardhat deploy plugin', or 'solidity deployment'. The terms are somewhat technical but appropriate for the domain. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: migrating hardhat-deploy from v1 to v2. This is unlikely to conflict with other skills due to the precise tool name and version-specific migration context. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is exceptionally thorough and actionable, providing complete executable examples for every aspect of the hardhat-deploy v1→v2 migration. However, it is severely over-engineered for a SKILL.md file — at roughly 1000+ lines it consumes enormous context window space, with significant redundancy across sections (patterns repeated in step-by-step, common patterns, and troubleshooting). The content would benefit enormously from splitting into multiple files with the SKILL.md serving as a concise overview.
Suggestions
Split into multiple files: keep SKILL.md as a ~150-line overview with the key differences table and step-by-step outline, then move detailed examples to referenced files like DEPLOY_SCRIPTS.md, TEST_CONVERSION.md, TROUBLESHOOTING.md, and ADVANCED.md
Eliminate redundancy: the same v1→v2 transformations appear in Step-by-Step, Common Patterns, and Troubleshooting sections — consolidate into one authoritative location and reference it
Remove content Claude doesn't need: the architecture comparison mermaid diagrams, 'When to Stay on v1' section, introduction/overview prose, and summary section add little actionable value
Condense the transformation rules: instead of listing 10+ bullet points after each code example, let the side-by-side code examples speak for themselves — Claude can infer the differences
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~1000+ lines. Contains massive amounts of redundancy — the same v1→v2 transformations are shown multiple times (in the step-by-step section, common patterns section, and troubleshooting section). Architecture diagrams, mermaid charts, 'when to stay on v1' advice, and explanatory prose like 'hardhat-deploy v2 is a complete rewrite' add little value for Claude. The transformation rules are repeated in prose after already being demonstrated in code examples. | 1 / 3 |
Actionability | Highly actionable with complete, executable code examples for every transformation. Both v1 and v2 patterns are shown side-by-side with explicit transformation rules. The deploy scripts, test conversions, config files, and tsconfig changes are all copy-paste ready with real import paths and realistic code. | 3 / 3 |
Workflow Clarity | The migration is clearly sequenced into 6 numbered steps with logical ordering (dependencies → config → deploy scripts → tests → scripts → package.json scripts). The comprehensive migration checklist at the end provides explicit verification checkpoints for each phase, including compilation, deployment, and type-checking validation steps. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload content into. The troubleshooting guide, advanced topics, common patterns, and architecture comparison sections could all be separate referenced files. Everything is inlined into a single massive document, making it extremely expensive in the context window. The table of contents helps navigation but doesn't solve the token cost problem. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (2033 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wighawag/hardhat-deploy
- Commit
e2395f0
- 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.