โ† All skills
Tencent SkillHub ยท Developer Tools

Ethereum Wingman

Ethereum development tutor and builder for Scaffold-ETH 2 projects. Triggers on "build", "create", "dApp", "smart contract", "Solidity", "DeFi", "Ethereum", "web3", or any blockchain development task. ALWAYS uses fork mode to test against real protocol state.

skill openclawclawhub Free
0 Downloads
0 Stars
0 Installs
0 Score
High Signal

Ethereum development tutor and builder for Scaffold-ETH 2 projects. Triggers on "build", "create", "dApp", "smart contract", "Solidity", "DeFi", "Ethereum", "web3", or any blockchain development task. ALWAYS uses fork mode to test against real protocol state.

โฌ‡ 0 downloads โ˜… 0 stars Unverified but indexed

Install for OpenClaw

Quick setup
  1. Download the package from Yavira.
  2. Extract the archive and review SKILL.md first.
  3. Import or place the package into your OpenClaw setup.

Requirements

Target platform
OpenClaw
Install method
Manual import
Extraction
Extract archive
Prerequisites
OpenClaw
Primary doc
SKILL.md

Package facts

Download mode
Yavira redirect
Package format
ZIP package
Source platform
Tencent SkillHub
What's included
AGENTS.md, SKILL.md, metadata.json, references/automation-and-incentives.md, references/critical-gotchas.md, references/historical-hacks.md

Validation

  • Use the Yavira download entry.
  • Review SKILL.md after the package is downloaded.
  • Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

  1. Download the package from Yavira.
  2. Extract it into a folder your agent can access.
  3. Paste one of the prompts below and point your agent at the extracted folder.
New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Trust & source

Release facts

Source
Tencent SkillHub
Verification
Indexed source record
Version
0.1.0

Documentation

ClawHub primary doc Primary doc: SKILL.md 22 sections Open source page

Ethereum Wingman

Comprehensive Ethereum development guide for AI agents. Covers smart contract development, DeFi protocols, security best practices, and the SpeedRun Ethereum curriculum.

Default Stack: Scaffold-ETH 2 with Fork Mode

When a user wants to BUILD any Ethereum project, follow these steps: Step 1: Create Project npx create-eth@latest # Select: foundry (recommended), target chain, project name Step 2: Fix Polling Interval Edit packages/nextjs/scaffold.config.ts and change: pollingInterval: 30000, // Default: 30 seconds (way too slow!) to: pollingInterval: 3000, // 3 seconds (much better for development) Step 3: Install & Fork a Live Network cd <project-name> yarn install yarn fork --network base # or mainnet, arbitrum, optimism, polygon Step 4: Enable Auto Block Mining (REQUIRED!) # In a new terminal, enable interval mining (1 block/second) cast rpc anvil_setIntervalMining 1 Without this, block.timestamp stays FROZEN and time-dependent logic breaks! Optional: Make it permanent by editing packages/foundry/package.json to add --block-time 1 to the fork script. Step 5: Deploy to Local Fork (FREE!) yarn deploy Step 6: Start Frontend yarn start Step 7: Test the Frontend After the frontend is running, open a browser and test the app: Navigate to http://localhost:3000 Take a snapshot to get page elements (burner wallet address is in header) Click the faucet to fund the burner wallet with ETH Transfer tokens from whales if needed (use burner address from page) Click through the app to verify functionality Use the cursor-browser-extension MCP tools for browser automation. See tools/testing/frontend-testing.md for detailed workflows.

DO NOT:

Run yarn chain (use yarn fork --network <chain> instead!) Manually run forge init or set up Foundry from scratch Manually create Next.js projects Set up wallet connection manually (SE2 has RainbowKit pre-configured)

Why Fork Mode?

yarn chain (WRONG) yarn fork --network base (CORRECT) โ””โ”€ Empty local chain โ””โ”€ Fork of real Base mainnet โ””โ”€ No protocols โ””โ”€ Uniswap, Aave, etc. available โ””โ”€ No tokens โ””โ”€ Real USDC, WETH exist โ””โ”€ Testing in isolation โ””โ”€ Test against REAL state

Address Data Available

Token, protocol, and whale addresses are in data/addresses/: tokens.json - WETH, USDC, DAI, etc. per chain protocols.json - Uniswap, Aave, Chainlink per chain whales.json - Large token holders for test funding

THE MOST CRITICAL CONCEPT

NOTHING IS AUTOMATIC ON ETHEREUM. Smart contracts cannot execute themselves. There is no cron job, no scheduler, no background process. For EVERY function that "needs to happen": Make it callable by ANYONE (not just admin) Give callers a REASON (profit, reward, their own interest) Make the incentive SUFFICIENT to cover gas + profit Always ask: "Who calls this function? Why would they pay gas?" If you can't answer this, your function won't get called.

Examples of Proper Incentive Design

// LIQUIDATIONS: Caller gets bonus collateral function liquidate(address user) external { require(getHealthFactor(user) < 1e18, "Healthy"); uint256 bonus = collateral * 5 / 100; // 5% bonus collateralToken.transfer(msg.sender, collateral + bonus); } // YIELD HARVESTING: Caller gets % of harvest function harvest() external { uint256 yield = protocol.claimRewards(); uint256 callerReward = yield / 100; // 1% token.transfer(msg.sender, callerReward); } // CLAIMS: User wants their own tokens function claimRewards() external { uint256 reward = pendingRewards[msg.sender]; pendingRewards[msg.sender] = 0; token.transfer(msg.sender, reward); }

1. Token Decimals Vary

USDC = 6 decimals, not 18! // BAD: Assumes 18 decimals - transfers 1 TRILLION USDC! uint256 oneToken = 1e18; // GOOD: Check decimals uint256 oneToken = 10 ** token.decimals(); Common decimals: USDC, USDT: 6 decimals WBTC: 8 decimals Most tokens (DAI, WETH): 18 decimals

2. ERC-20 Approve Pattern Required

Contracts cannot pull tokens directly. Two-step process: // Step 1: User approves token.approve(spenderContract, amount); // Step 2: Contract pulls tokens token.transferFrom(user, address(this), amount); Never use infinite approvals: // DANGEROUS token.approve(spender, type(uint256).max); // SAFE token.approve(spender, exactAmount);

3. No Floating Point in Solidity

Use basis points (1 bp = 0.01%): // BAD: This equals 0 uint256 fivePercent = 5 / 100; // GOOD: Basis points uint256 FEE_BPS = 500; // 5% = 500 basis points uint256 fee = (amount * FEE_BPS) / 10000;

4. Reentrancy Attacks

External calls can call back into your contract: // SAFE: Checks-Effects-Interactions pattern function withdraw() external nonReentrant { uint256 bal = balances[msg.sender]; balances[msg.sender] = 0; // Effect BEFORE interaction (bool success,) = msg.sender.call{value: bal}(""); require(success); } Always use OpenZeppelin's ReentrancyGuard.

5. Never Use DEX Spot Prices as Oracles

Flash loans can manipulate spot prices instantly: // SAFE: Use Chainlink function getPrice() internal view returns (uint256) { (, int256 price,, uint256 updatedAt,) = priceFeed.latestRoundData(); require(block.timestamp - updatedAt < 3600, "Stale"); require(price > 0, "Invalid"); return uint256(price); }

6. Vault Inflation Attack

First depositor can steal funds via share manipulation: // Mitigation: Virtual offset function convertToShares(uint256 assets) public view returns (uint256) { return assets.mulDiv(totalSupply() + 1e3, totalAssets() + 1); }

7. Use SafeERC20

Some tokens (USDT) don't return bool on transfer: import "@openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol"; using SafeERC20 for IERC20; token.safeTransfer(to, amount); // Handles non-standard tokens

Project Structure

packages/ โ”œโ”€โ”€ foundry/ # Smart contracts โ”‚ โ”œโ”€โ”€ contracts/ # Your Solidity files โ”‚ โ””โ”€โ”€ script/ # Deploy scripts โ””โ”€โ”€ nextjs/ โ”œโ”€โ”€ app/ # React pages โ””โ”€โ”€ contracts/ # Generated ABIs + externalContracts.ts

Essential Hooks

// Read contract data const { data } = useScaffoldReadContract({ contractName: "YourContract", functionName: "greeting", }); // Write to contract const { writeContractAsync } = useScaffoldWriteContract("YourContract"); // Watch events useScaffoldEventHistory({ contractName: "YourContract", eventName: "Transfer", fromBlock: 0n, });

SpeedRun Ethereum Challenges

Reference these for hands-on learning: ChallengeConceptKey Lesson0: Simple NFTERC-721Minting, metadata, tokenURI1: StakingCoordinationDeadlines, escrow, thresholds2: Token VendorERC-20Approve pattern, buy/sell3: Dice GameRandomnessOn-chain randomness is insecure4: DEXAMMx*y=k formula, slippage5: OraclesPrice FeedsChainlink, manipulation resistance6: LendingCollateralHealth factor, liquidation incentives7: StablecoinsPeggingCDP, over-collateralization8: Prediction MarketsResolutionOutcome determination9: ZK VotingPrivacyZero-knowledge proofs10: MultisigSignaturesThreshold approval11: SVG NFTOn-chain ArtGenerative, base64 encoding

Uniswap (AMM)

Constant product formula: x * y = k Slippage protection required LP tokens represent pool share

Aave (Lending)

Supply collateral, borrow assets Health factor = collateral value / debt value Liquidation when health factor < 1

ERC-4626 (Tokenized Vaults)

Standard interface for yield-bearing vaults deposit/withdraw with share accounting Protect against inflation attacks

Security Review Checklist

Before deployment, verify: Access control on all admin functions Reentrancy protection (CEI + nonReentrant) Token decimal handling correct Oracle manipulation resistant Integer overflow handled (0.8+ or SafeMath) Return values checked (SafeERC20) Input validation present Events emitted for state changes Incentives designed for maintenance functions

Response Guidelines

When helping developers: Follow the fork workflow - Always use yarn fork, never yarn chain Answer directly - Address their question first Show code - Provide working examples Warn about gotchas - Proactively mention relevant pitfalls Reference challenges - Point to SpeedRun Ethereum for practice Ask about incentives - For any "automatic" function, ask who calls it and why

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package
5 Docs1 Config
  • SKILL.md Primary doc
  • AGENTS.md Docs
  • references/automation-and-incentives.md Docs
  • references/critical-gotchas.md Docs
  • references/historical-hacks.md Docs
  • metadata.json Config