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.

1.34x

Quality

73%

Does it follow best practices?

Impact

94%

1.34x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/blockchain-web3/skills/web3-testing/SKILL.md

The canonical home for this skill is web3-testing in wshobson/agents

Quality

Content

53%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 content is rich with executable, copy-paste-ready code examples but is over-long and behaves as a monolithic reference rather than a lean overview. The biggest issue is that the advertised bundle files do not exist and their would-be content is inlined into SKILL.md.

Suggestions

Create the advertised bundle files (references/hardhat-setup.md, foundry-setup.md, test-patterns.md, mainnet-forking.md, contract-verification.md, assets/hardhat-config.js, test-suite.js, foundry.toml, scripts/test-contract.sh) and move the full configs and complete test suites out of SKILL.md into them, leaving only concise overview snippets inline.

Replace stub test bodies (e.g. "// Test functionality", "// Should swap on Uniswap") and "0x..." placeholders with complete, runnable assertions or explicitly mark them as illustrative skeletons.

Add a brief sequenced testing workflow with validation checkpoints (write tests → run `npx hardhat test` → check coverage → fix failures → re-run) so the multi-step process is explicit rather than implied by scattered pattern sections.

Dimension	Reasoning	Score
Conciseness	The body inlines full configuration files and complete test suites (~410 lines) that could be tightened or moved to bundle files; prose is mostly lean but the volume of inlined reference material keeps it at the level-3 "mostly efficient but could be tightened" anchor rather than 4.	3 / 5
Actionability	Most sections provide copy-paste ready, executable code (hardhat.config.js, Chai tests, Forge tests, CI YAML), but some examples are stubs ("// Test functionality", "// Should swap on Uniswap" with empty bodies, "0x..." placeholders), placing it at level 4 with minor gaps rather than fully complete at 5.	4 / 5
Workflow Clarity	The document is a catalog of testing patterns rather than a sequenced workflow; the CI/CD section gives a rough sequence but there are no validation checkpoints or validate→fix→retry feedback loops for the test cycle, matching the level-3 anchor of listed steps with missing checkpoints.	3 / 5
Progressive Disclosure	The "Resources" section signals nine bundle files (references/.md, assets/.js, scripts/*.sh) but none exist on disk, and large reference material (full configs and test suites) that belongs in those separate files is inlined, matching the level-2 anchor of inlined content that clearly belongs in separate files.	2 / 5
	Total	12 / 20 Passed

Description

92%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, well-structured description that clearly answers both what the skill does and when to use it with concrete, natural trigger terms. Minor keyword variations could be added but it is largely exemplary.

Dimension	Reasoning	Score
Specificity	"Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking" lists multiple concrete testing actions with comprehensive coverage of testing modes, matching the level-5 anchor rather than 4 because no meaningful testing action category is missing.	5 / 5
Completeness	It explicitly states 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 concrete trigger phrases, exactly matching the level-5 anchor.	5 / 5
Trigger Term Quality	"testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols" plus Hardhat/Foundry/mainnet forking gives good natural keyword coverage, but a few common variants (e.g. file extensions like .sol, "fuzz testing") are absent, placing it just below the comprehensive level-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The web3/Solidity/Hardhat/Foundry/DeFi niche is specific with distinct triggers and minimal overlap risk with general-purpose skills, matching the level-5 "clear niche" anchor rather than the level-4 "minor overlap risk" anchor.	5 / 5
	Total	19 / 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
referenced_paths_exist	Referenced path issues: 9 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/blockchain-web3/skills/web3-testing/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours 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.