Solidity Testing
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any test files (*.t.sol). Covers test structure, naming conventions, coverage requirements, fuzz testing, and Foundry cheatcodes. Trigger: any task involving creating, editing, or running Solidity tests.
Install
npx skills add NeverSight/learn-skills.dev --skill solidity-testinggit clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git /tmp/learn-skills.dev
mkdir -p ~/.claude/skills
cp -r /tmp/learn-skills.dev/data/skills-md/0xlayerghost/solidity-agent-kit/solidity-testing ~/.claude/skills/solidity-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Testing Standards ## Language Rule - **Always respond in the same language the user is using.** If the user asks in Chinese, respond in Chinese. If in English, respond in English. ## Test Organization - **One test contract per source contract**: `MyToken.sol` → `MyToken.t.sol` - **File location**: All tests in `test/` directory - **Naming**: `test_<feature>_<scenario>` for passing tests, `testFail_<feature>_<scenario>` for expected reverts - Example: `test_transfer_revertsWhenInsufficientBalance` - Example: `test_stake_updatesBalanceCorrectly` - **Independence**: Each test must run in isolation — use `setUp()` for shared state, no cross-test dependencies - **Filtering**: Support `--match-test` and `--match-contract` for targeted runs ## Coverage Requirements Every core function must have tests covering: | Scenario | What to verify | |----------|---------------| | Happy path | Standard input → expected output, correct state changes | | Permission checks | Unauthorized caller → `vm.expectRevert` with correct error | | Boundary conditions | Zero values, max values (`type(uint256).max`), off-by-one | | Failure scenarios | Every `require` / `revert` / custom error path | | State changes | Storage updates, balance changes, event emissions (`vm.expectEmit`) | | Edge cases | Empty arrays, duplicate calls, self-transfers | ## Foundry Cheatcodes Quick Reference | Cheatcode | Usage | |-----------|-------| | `vm.prank(addr)` | Next call from `addr` |
Details
- Skill name
solidity-testing- Repository
- NeverSight/learn-skills.dev
- Path
data/skills-md/0xlayerghost/solidity-agent-kit/solidity-testing/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Solidity Testing skill do?
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any test files (*.t.sol). Covers test structure, naming conventions, coverage requirements, fuzz testing, and Foundry cheatcodes. Trigger: any task involving creating, editing, or running Solidity tests.
How do I install the Solidity Testing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add NeverSight/learn-skills.dev --skill solidity-testing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Solidity Testing popular?
It lives in NeverSight/learn-skills.dev, which has 223 GitHub stars and 42 forks.
Related skills
Council
223NeverSight/learn-skills.dev
Convene the Council of High Intelligence — multi-persona deliberation with historical thinkers for deeper analysis of complex problems.
Megaeth Developer
223NeverSight/learn-skills.dev
End-to-end MegaETH development playbook (Feb 2026). Covers wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync (EIP-7966) for instant receipts, JSON-RPC batching, real-time mini-block subscriptions, storage-aware contract patterns (Solady RedBlackTreeLib), MegaEVM gas model, WebSocket keepalive, bridging from Ethereum, and debugging with mega-evme. Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts.
Openclaw Stock Skill
223NeverSight/learn-skills.dev
使用 data.diemeng.chat 提供的接口查询股票日线、分钟线、财务指标等数据,支持 A 股等市场。
Token Antiflash
223NeverSight/learn-skills.dev
[AUTO-INVOKE] MUST be invoked when designing or reviewing ERC20 token contracts that need flash loan protection. Covers token-level defense design patterns: cost tracking, same-block cooldown, progressive sell tax, minimum balance retention, EIP-7702 aware address checks, front-run protection, and referral binding. Trigger: any ERC20 token with anti-flash-loan, anti-bot, or tokenomics security design requirements.
Solidity Security
223NeverSight/learn-skills.dev
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any Solidity contract (.sol files). Covers private key handling, access control, reentrancy prevention, gas safety, and pre-audit checklists. Trigger: any task involving creating, editing, or reviewing .sol source files.
Trading Wisdom
223NeverSight/learn-skills.dev
Core trading insights learned from Agent Arena competition. Use when making any trading decision to apply institutional knowledge.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.