blockchain-web3

Guide Solidity and Web3 protocol creation with Foundry testing and security checks.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill blockchain-web3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blockchain-web3
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/blockchain-web3
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill blockchain-web3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design, implement, debug, and verify Solidity smart contracts and common Web3 protocol patterns without getting stuck on the many framework, security, and testing decisions.

Core Features & Use Cases

  • Architecture decision support: Choose the right contract standard and protocol shape for tokens, NFTs, DeFi components, governance, bridges, and smart-account flows (ERC-20/721/1155, ERC-4626, ERC-4337, Governor/Timelock).
  • Testing and verification guidance: Map unit/integration/fork/invariant/fuzz/formal-security approaches to the right toolchain (Foundry, slither, symbolic/static checks).
  • Security and gas-focused implementation patterns: Apply CEI and reentrancy protections, access control best practices, anti-MEV/oracle guidance, and common gas optimizations.

Quick Start

Use the blockchain-web3 skill to plan and implement a secure ERC-20 staking contract with Foundry tests, including a fuzz/invariant strategy and a security checklist for reentrancy, access control, and oracle assumptions.

Frequently Asked Questions about blockchain-web3

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

FAQPage Schema
How do I build and secure a Solidity smart contract for a DeFi protocol?

To build and secure Solidity smart contracts, apply Checks-Effects-Interactions patterns, role-based access control, and reentrancy guards. Architecture selection and testing via Foundry ensure components like ERC-4626 vaults are secure across EVM and L2 environments.

What is the best way to test Web3 smart contracts using Foundry?

Testing Web3 smart contracts via Foundry involves mapping unit, integration, fork, invariant, and fuzz tests. This strategy verifies protocol assumptions and validates logic across different EVM environments before deployment.

How do I optimize gas and reduce protocol risk for EVM and L2 environments?

Optimizing gas and reducing protocol risk requires applying Solidity 0.8.x best practices and common gas optimizations. Security checks via static analysis tools like Slither or Mythril identify vulnerabilities early in the development lifecycle.

Can I use this approach for ERC-4337 account abstraction and governance contracts?

Yes, this approach supports architecture decisions for ERC-4337 account abstraction, Governor and Timelock governance, bridges, and various token standards. It guides implementation planning and security verification for these specific Web3 protocol patterns.

What security checks should I run to prevent reentrancy and oracle manipulation?

Security checks to prevent reentrancy and oracle manipulation involve applying reentrancy protections, anti-MEV guidance, and verifying oracle assumptions. Tools like Slither and Mythril perform static and symbolic checks to reduce protocol risk.

Why does my smart contract architecture selection matter for NFT and token standards?

Smart contract architecture selection matters because choosing the right standard—like ERC-20, ERC-721, or ERC-1155—defines protocol shape and security boundaries. Proper selection streamlines implementation planning and testing for tokens and NFTs.