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.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A largely actionable, well-structured skill with strong executable examples and clean one-level-deep reference structure. It loses points on conciseness due to stubbed test bodies and restated description, and on workflow clarity due to missing validation checkpoints for risky operations.

Suggestions

Replace stubbed test bodies (time-locked operations, Uniswap swap) with real assertions, and fix the undefined `addr1` in the gas test so the example actually runs.

Add explicit validation/checkpoint steps for risky flows — e.g. after mainnet forking confirm the fork block, and after Etherscan verification poll the verified status — to lift workflow clarity.

Trim the restated description in the intro and 'When to Use' list, since the frontmatter already covers triggers.

DimensionReasoningScore

Conciseness

The body is mostly tight executable code with little prose, but it restates the description in the intro and 'When to Use' list, and includes stubbed test bodies (e.g. '// Test time-dependent functionality', '// Test with real Uniswap contracts') plus an undefined `addr1` reference in the gas test.

2 / 3

Actionability

Provides complete, copy-paste-ready code — full hardhat.config.js, Chai/Mocha unit patterns, and a complete Foundry TokenTest with fuzzing, cheatcodes, and mainnet forking — with only a few clearly-marked placeholder stubs.

3 / 3

Workflow Clarity

Content is organized by topic (setup, unit tests, Foundry, advanced patterns) but lacks an explicit sequenced process with validation checkpoints for risky operations like mainnet forking and contract verification, which per the rubric caps this dimension at 2.

2 / 3

Progressive Disclosure

Well-organized into clear sections with a single well-signaled one-level-deep reference to references/details.md, which I verified exists and holds genuinely supplementary content (gas optimization, coverage, verification, CI/CD).

3 / 3

Total

10

/

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.

A strong, well-structured description that concisely states concrete capabilities, includes natural trigger terms, and clearly answers both what and when. It occupies a distinct niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'unit tests, integration tests, and mainnet forking' — alongside named tools (Hardhat, Foundry), matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Test smart contracts comprehensively using Hardhat and Foundry...') and when ('Use when testing Solidity contracts...'), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Includes natural user phrasing such as 'testing Solidity contracts', 'setting up blockchain test suites', and 'validating DeFi protocols', giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — Solidity/DeFi smart-contract testing with Hardhat/Foundry — with distinct triggers unlikely to fire for unrelated testing skills.

3 / 3

Total

12

/

12

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.