Skills web3-testing
๐Ÿ“ฆ

web3-testing

Content revision r1 Safe โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access๐Ÿ”‘ Env variables

Test Smart Contracts With Hardhat and Foundry

Smart contract teams need repeatable tests for contracts, DeFi integrations, gas costs, and forked networks. This skill provides testing patterns, setup guidance, and verification workflows for Hardhat and Foundry.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "web3-testing" from https://skillstore.io/skills/sickn33-web3-testing.md and its manifest at https://skillstore.io/api/skills/sickn33-web3-testing/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "web3-testing". A developer asks for Hardhat tests for an ERC20 token.

Expected outcome:

A test plan covering deployment, initial balances, transfers, revert cases, events, and gas usage checks.

Using "web3-testing". A protocol engineer asks for a forked Uniswap integration test.

Expected outcome:

A scenario list that resets a mainnet fork, connects to live token contracts, performs swaps, and verifies balances.

Using "web3-testing". A team asks how to add coverage to CI.

Expected outcome:

A workflow outline that compiles contracts, runs tests, generates coverage, and uploads reports.

Security Audit

Safe
v5 โ€ข 7/7/2026 Open versioned report

The static alerts are false positives caused by Markdown fences, tutorial code snippets, placeholder RPC URLs, and environment variable examples. I found no prompt injection, secret exfiltration, unauthorized execution, or malicious intent in SKILL.md. The author should add clearer guidance for placeholders, missing resources, and private key hygiene.

1
Files scanned
428
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-web3-testing/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-web3-testing/security.svg)](https://skillstore.io/skills/sickn33-web3-testing?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-web3-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-web3-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-web3-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). web3-testing security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-web3-testing/audits/5

BibTeX citation

@techreport{sickn33-sickn33-web3-testing-2026, author = {sickn33}, title = {web3-testing security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-web3-testing/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "web3-testing security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-07" url: "https://skillstore.io/skills/sickn33-web3-testing/audits/5" identifiers: - type: other value: "skillstore:sickn33-web3-testing:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
wshobson Recommended

wshobson-web3-testing

Skillstore Score 78
Evidence Confidence High
Skillstore usage 14
Updated

2026-08-21

sickn33 Current

sickn33-web3-testing

Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Build a Solidity test suite

Create coverage for deployment, ownership, token transfers, event emissions, revert paths, and time-based logic.

Validate DeFi integrations

Design mainnet fork tests that interact with real protocol contracts and pinned block numbers.

Add CI coverage checks

Plan automated compile, test, gas, coverage, and reporting steps for pull requests.

Try These Prompts

Create a first unit test
Help me write beginner Hardhat tests for this Solidity contract. Cover deployment, ownership, transfers, events, and expected reverts.
Add Foundry fuzz coverage
Design Foundry tests for this contract. Include setup, prank usage, balance assertions, expected reverts, and fuzz cases for boundary values.
Plan mainnet fork scenarios
Create a mainnet fork testing plan for this DeFi workflow. Include pinned blocks, contract addresses, impersonation needs, and balance assertions.
Review testing strategy
Review my smart contract testing strategy. Identify missing unit, integration, fuzz, fork, gas, access control, and CI coverage.

Best Practices

  • Use fixtures to isolate state and make tests repeatable.
  • Use mainnet forks only with pinned block numbers and documented RPC configuration.
  • Keep private keys and API keys outside source control and use test wallets.

Avoid

  • Do not rely only on happy path unit tests for value-moving contracts.
  • Do not run fork tests against floating latest blocks when results must be reproducible.
  • Do not place real private keys, RPC keys, or deployment secrets in shared examples.

Frequently Asked Questions

Which frameworks does this skill cover?
It covers Hardhat and Foundry testing patterns for Solidity smart contracts.
Can it help with mainnet fork tests?
Yes. It explains fork setup, pinned blocks, existing contract addresses, and account impersonation patterns.
Does this skill audit contract security?
No. It helps design tests, but it does not replace a security audit.
Does it require private keys?
Most local tests do not need private keys. Deployment and verification examples should use test wallets and environment variables.
Can it support CI pipelines?
Yes. It includes guidance for compile, test, coverage, and report upload steps.
Can it prove a protocol is economically safe?
No. Tests reduce risk, but economic safety needs deeper modeling, review, and monitoring.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

f93e9bb0daca99badb6a7e574b97737155d57cb3

Maintenance freshness

7/18/2026

Usage

7 downloads ยท 147 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all