solidity-web3

Develops and audits Solidity smart contracts with Foundry security testing.

22|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/Lynricsy/HyperSkills --skill solidity-web3-lynricsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solidity-web3
Source: https://github.com/Lynricsy/HyperSkills/tree/main/skills/solidity-web3
Command: npx skills add https://github.com/Lynricsy/HyperSkills --skill solidity-web3-lynricsy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing and reviewing EVM smart contracts without a systematic method misses the vulnerability classes that actually lose funds: reentrancy in all four shapes, proxy storage collisions, silent cast truncation, oracle manipulation, and non-standard ERC-20 behavior. This Skill provides verified, version-specific rules and workflows for developing, reviewing, upgrading, and testing Solidity contracts defensively. ## Core Features & Use Cases - Contract review workflow: Inventory entry points, run Slither first, walk vulnerability classes by realized losses, and ship every finding with a Foundry test that fails before the fix and passes after. - Upgrade safety checks: Diff storage layouts with forge inspect, verify _authorizeUpgrade gating and _disableInitializers(), and fork-test the real proxy before upgrading. - Foundry testing discipline: Handler-based invariant suites, bound-based fuzzing, precise revert assertions, and reading the per-selector calls/reverts table as evidence. - Use Case: Given a vault contract holding user ETH, produce a review that identifies the reentrancy drain, the read-only reentrancy affecting integrators, and the missing access control, each with a reproducing Foundry test. ## Quick Start Ask the agent to review your Solidity contract for security issues before deployment, and it will apply the vulnerability checklist, run Slither, and write reproducing Foundry tests for each finding.

Frequently Asked Questions about solidity-web3

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a Solidity smart contract for reentrancy?

Inventory every external and public function including callbacks, then check that state writes precede external calls (checks-effects-interactions) and that view functions integrators read carry the same guard. Reproduce each candidate as a Foundry test with an attacker contract whose receive() re-enters.

How do I safely upgrade a contract behind an ERC-1967 proxy?

Diff storage layouts with forge inspect on both versions and require append-only changes, verify _authorizeUpgrade is gated and _disableInitializers() is in the constructor, then fork mainnet and re-read user balances through the upgraded proxy before deploying.

What changed in OpenZeppelin Contracts 5.x for access control?

Ownable requires an initialOwner constructor argument, reverts use custom errors like OwnableUnauthorizedAccount instead of strings, and ReentrancyGuard moved from contracts/security/ to contracts/utils/. Tests asserting 4.x revert strings test nothing.

Why does my Foundry invariant test pass but prove nothing?

The [invariant] fail_on_revert config defaults to false, so a handler whose every call reverts still prints a green [PASS]. Read the per-selector calls/reverts table to confirm calls actually landed before treating the run as evidence.

Does this skill cover non-EVM chains like Solana or Move?

No. The skill covers only EVM-and-Solidity contracts verified against Solidity 0.8.37, OpenZeppelin 5.7.0, Foundry 1.8.1, and Slither 0.11.6. Solana, Cairo, Move, and CosmWasm are explicitly out of scope.

Can I use this skill to exploit a deployed contract?

No. The skill is defensive only: reproduction happens locally via Foundry tests, forks of public state, or local anvil. Broadcasting transactions against contracts you do not control or extracting value from others' transactions is explicitly out of scope.