CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/blockchain-web3/skills/web3-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

An actionable, code-heavy skill body with good structure and a clear reference pointer, weakened by missing workflow sequencing/validation and a few stub test bodies. Shifting more pattern code into details.md and adding an explicit test-run/coverage feedback loop would raise the weaker dimensions.

Suggestions

Add an explicit sequenced workflow with a validation checkpoint, e.g. write tests -> run `npx hardhat test` / `forge test` -> check `solidity-coverage` output -> fix gaps -> re-run.

Fill in or remove stub test bodies (e.g. "Should swap on Uniswap", "Should handle time-locked operations") so every example is fully executable.

Move some of the inlined advanced patterns (snapshot/revert, mainnet forking, impersonation) into references/details.md to tighten SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

Body is almost entirely executable code with minimal prose padding and no exposition of concepts Claude already knows; a few stub comments and the sheer inlined volume keep it just below a 5.

4 / 5

Actionability

Provides copy-paste-ready Hardhat config, Chai unit tests, and Foundry/Forge tests with fuzzing and cheatcodes, but several examples have empty or placeholder bodies ("Should swap on Uniswap", "Should handle time-locked operations").

4 / 5

Workflow Clarity

Content is organized as a topic catalog (setup, unit tests, Foundry, advanced patterns) rather than a sequenced workflow, and lacks explicit validation/checkpoint steps such as run-tests-then-check-coverage feedback loops.

3 / 5

Progressive Disclosure

Clear section headers and a well-signaled one-level-deep pointer to references/details.md; however a large amount of pattern code is inlined in SKILL.md that could live in the reference file.

4 / 5

Total

15

/

20

Passed

Description

87%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.

A strong, third-person description that clearly states both capability and trigger conditions with concrete, domain-specific keywords. Minor gains available by trimming "comprehensively" and adding a few more synonyms.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions (unit tests, integration tests, mainnet forking) plus the two tools, but "comprehensively" is vague padding and fuzzing/coverage/gas testing are absent from the description.

4 / 5

Completeness

Explicitly answers both what ("Test smart contracts ... 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 concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ("testing Solidity contracts", "blockchain test suites", "validating DeFi protocols", Hardhat, Foundry), but misses common synonyms like "smart contract tests" or "Ethereum testing".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (smart-contract testing with Hardhat/Foundry and mainnet forking) with distinct triggers and minimal overlap risk against general development skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.