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

—

Does it follow best practices?

Impact

94%

1.34x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a broad, mostly executable reference of Hardhat and Foundry testing patterns, but it suffers from verbosity, several incomplete/buggy code stubs, no sequenced workflow with validation checkpoints, and a Resources section pointing to bundle files that do not exist on disk.

Suggestions

Create the referenced bundle files (references/*.md, assets/*, scripts/test-contract.sh) or remove the dangling 'Resources' links, and move the full configs and test suites into those files so SKILL.md stays a lean overview.

Fix or complete the stubbed examples: add assertions to the time-locked and Uniswap fork tests and define addr1 in the gas-optimization test so every code block is actually runnable.

Tighten the body by removing comments that restate obvious concepts and move time-sensitive details (Solidity 0.8.19, Node 16, deprecated Goerli, the pinned blockNumber) into a versioned/deprecated section or a reference file.

Dimension	Reasoning	Score
Conciseness	The ~410-line body is padded with comments restating obvious concepts ('// Fixture for test setup', '// Give ETH to address') and inlines full configs/contracts, with version-sensitive details (Solidity 0.8.19, Node 16, deprecated Goerli) inline rather than in a deprecated section; useful but not lean enough for a 3.	2 / 3
Actionability	Most code blocks are executable and copy-paste ready, but several examples are incomplete: the time-locked and Uniswap fork tests have no assertions (just '// Test...' stubs), and the gas-optimization test references an undefined addr1, constituting missing key details that prevent a clean 3.	2 / 3
Workflow Clarity	Content is organized by topic but presented as a pattern catalog rather than a sequenced testing workflow, with no validation checkpoints or feedback loops for risky operations (forking, coverage, CI); per the guideline, missing validation in batch/destructive contexts caps this at 2.	2 / 3
Progressive Disclosure	The 'Resources' section explicitly signals eight one-level-deep bundle files, but none of the referenced references/, assets/, or scripts/ directories or files exist on disk, and the body inlines large blocks (full configs, full test suites) that should live in those separate files; clearly signaled references keep it above 1, but dangling files and heavy inlining block a 3.	2 / 3
	Total	8 / 12 Passed

Description

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.

The description is well-crafted: it states concrete capabilities, lists natural trigger terms, and provides an explicit 'Use when...' clause. It is concise, distinctive, and free of vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names concrete tools (Hardhat, Foundry) and several specific actions (unit tests, integration tests, mainnet forking), matching the 'lists multiple specific concrete actions' anchor; clearly above the 'some actions, not comprehensive' level.	3 / 3
Completeness	Explicitly states what it does (test smart contracts with Hardhat/Foundry and named test types) and when to use it via an explicit 'Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols' clause, matching the top anchor exactly.	3 / 3
Trigger Term Quality	Includes natural terms users would say ('testing Solidity contracts', 'DeFi protocols', 'Hardhat', 'Foundry', 'smart contracts') with good coverage of common variations; not limited to jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Web3/smart-contract niche with distinct triggers (Solidity, Hardhat, Foundry, DeFi) unlikely to overlap with non-Web3 skills.	3 / 3
	Total	12 / 12 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
Commit: abece4a

Reviewed: 4 days 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.