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
76
65%
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 actions and occupying a clear niche (hardhat-deploy v1 to v2 migration), making it distinctive and specific. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill, and could benefit from additional natural trigger terms users might use.
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 deployment migration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'dependency updates, configuration restructuring, deploy script conversion, test updates, and troubleshooting'. These are clear, actionable tasks within the migration process. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (migrating hardhat-deploy v1 to v2 with specific subtasks), 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 relevant to 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
62%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 before/after code examples for every aspect of the migration. However, it is severely over-length with significant redundancy—the same transformations are shown in the step-by-step guide, common patterns, and troubleshooting sections. The content would benefit enormously from being split into multiple files and deduplicated, reducing token consumption by potentially 50-60% without losing any actionable information.
Suggestions
Split into multiple files: keep SKILL.md as a concise overview with the key differences table and step-by-step outline, then link to separate files like DEPLOY_SCRIPTS.md, TESTS.md, TROUBLESHOOTING.md, and ADVANCED.md
Eliminate redundancy: the Common Patterns section largely duplicates the Step-by-Step Migration examples—consolidate into one location and reference it
Remove explanatory prose that Claude doesn't need (e.g., 'hardhat-deploy v2 is a complete rewrite that requires...', 'The migration requires significant changes, but results in...', architecture comparison mermaid diagrams)
Cut the Summary section and 'When to Stay on v1' advice—these are decision-making concerns for humans, not actionable migration instructions for Claude
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~1000+ lines. Contains extensive redundancy: transformation rules are repeated alongside before/after examples, the same patterns appear in multiple sections (e.g., proxy deployment shown in Step 3, Common Patterns, and Troubleshooting). Architecture diagrams, mermaid charts, and explanatory prose add bulk without proportional value. Claude doesn't need explanations of what ESM is or why TypeScript types are useful. | 1 / 3 |
Actionability | Highly actionable with complete, executable code examples for every transformation. Before/after patterns are concrete and copy-paste ready. Specific package versions, file paths, import statements, and CLI commands are all provided. The transformation rules are explicit and mechanical. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential migration process with a comprehensive checklist organized into 8 phases with verification steps. Each phase has explicit validation (Phase 7 includes compile, deploy, test, and type-check verification). The troubleshooting section provides error-to-solution mappings for common failure modes. | 3 / 3 |
Progressive Disclosure | Has a table of contents and logical section organization, but everything is crammed into a single massive file. The Advanced Topics, Troubleshooting, and Common Patterns sections could easily be separate files linked from the main skill. References to external repos are present but the skill itself doesn't split its own content appropriately for its length. | 2 / 3 |
Total | 9 / 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
a1cee92
- 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.