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.

62

Quality

74%

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 ./skills/web3-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A content-rich, actionable skill body that is undermined by broken bundle references and lack of a sequenced workflow with validation. Splitting inlined code into the referenced (currently missing) files and adding verification checkpoints would materially raise quality.

Suggestions

Create the referenced bundle files (references/*.md, assets/*.js, assets/foundry.toml, scripts/test-contract.sh) or remove the 'Resources' links, since they currently point to non-existent files.

Move the bulk of the inlined code examples into those reference files so SKILL.md stays a lean overview, raising progressive_disclosure.

Replace the generic 'Instructions' boilerplate with a concrete, sequenced test-setup workflow that includes validation checkpoints (e.g., compile -> run tests -> check coverage -> verify on Etherscan).

DimensionReasoningScore

Conciseness

The body is code-forward and mostly assumes Claude's competence, but the generic 'Instructions' boilerplate ('Apply relevant best practices and validate outcomes') and repeated sections (gas optimization and mainnet forking each appear twice) could be trimmed.

4 / 5

Actionability

Provides extensive copy-paste-ready Hardhat, Foundry, coverage, verification, and CI/CD examples, with minor gaps such as placeholder addresses ('0x...') and comment-only test bodies ('// Test time-dependent functionality').

4 / 5

Workflow Clarity

Only a vague three-step 'Instructions' sequence is present, with no validation checkpoints or feedback loops for the test-setup workflow; the body is more a pattern catalog than a sequenced process.

3 / 5

Progressive Disclosure

The 426-line body inlines content that belongs in separate reference files, and the 'Resources' section points to references/, assets/, and scripts/ files that do not exist in the bundle.

2 / 5

Total

13

/

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, well-structured description that clearly communicates capability and trigger conditions for a distinct web3 testing niche. Minor improvements could add fuzzing/coverage/gas mentions and a few more synonyms.

DimensionReasoningScore

Specificity

Names the domain and tools (Hardhat, Foundry) plus three concrete actions ('unit tests, integration tests, and mainnet forking'), with minor gaps such as fuzzing, coverage, and gas testing.

4 / 5

Completeness

Explicitly states both what it does ('Test smart contracts comprehensively using Hardhat and Foundry...') and when to use it ('Use when testing Solidity contracts...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('testing Solidity contracts', 'setting up blockchain test suites', 'validating DeFi protocols') plus tool names, though a few synonyms or file extensions are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear web3 smart-contract testing niche with distinct triggers (Hardhat, Foundry, Solidity, DeFi), making overlap with unrelated skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 9 missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-skills
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.