web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
Overall
score
86%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 94%
↑ 1.24xAgent success when using this skill
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (testing types, tools), includes natural trigger terms that blockchain developers would use, explicitly states both what it does and when to use it, and occupies a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Test smart contracts comprehensively', 'unit tests, integration tests, and mainnet forking', names specific tools (Hardhat and Foundry), and mentions specific use cases like 'validating DeFi protocols'. | 3 / 3 |
Completeness | Clearly answers both what ('Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking') and when ('Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'smart contracts', 'Hardhat', 'Foundry', 'unit tests', 'integration tests', 'mainnet forking', 'Solidity contracts', 'blockchain test suites', 'DeFi protocols'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on blockchain/smart contract testing with specific tools (Hardhat, Foundry) and technologies (Solidity, DeFi). Unlikely to conflict with general testing skills or other development skills due to highly specific domain terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent executable code examples covering both major testing frameworks. The main weaknesses are some verbosity in introductory sections and lack of explicit workflow sequencing with validation checkpoints for the overall testing process. The progressive disclosure and reference structure are well done.
Suggestions
Add a 'Quick Start Workflow' section at the top with numbered steps and validation checkpoints (e.g., 1. Install deps, 2. Compile and verify no errors, 3. Run tests, 4. Check coverage meets threshold)
Remove or condense the 'When to Use This Skill' section - these use cases are self-evident from the title
Add explicit validation steps like 'Run `npx hardhat compile` and verify 0 errors before proceeding to tests'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity. The 'When to Use This Skill' section lists obvious use cases, and some code examples could be more condensed. However, it avoids explaining basic concepts Claude would know. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples for both Hardhat and Foundry. Configuration files, test patterns, CI/CD workflows, and CLI commands are all copy-paste ready with realistic, complete implementations. | 3 / 3 |
Workflow Clarity | While individual testing patterns are clear, there's no explicit workflow sequence for setting up a test suite from scratch. Missing validation checkpoints between steps (e.g., verify compilation before testing, check coverage thresholds before deployment). | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from setup to advanced patterns. References section at the end provides one-level-deep links to detailed materials. Content is appropriately organized with logical groupings. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.