Skip to content

baneeishaque/ljt-520_openclaw-backup / skills/0xbreadguy/megaeth-ai-developer-skills

megaeth-developer

Unverified

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.

MegaETH Development Skill

What this Skill is for

Use this Skill when the user asks for:

  • Wallet setup and management on MegaETH
  • Sending transactions, checking balances, token operations
  • Token swaps via Kyber Network aggregator
  • MegaETH dApp frontend (React / Next.js with real-time updates)
  • RPC configuration and transaction flow optimization
  • Smart contract development with MegaEVM considerations
  • Storage optimization (avoiding expensive SSTORE costs)
  • Gas estimation and fee configuration
  • Testing and debugging MegaETH transactions
  • WebSocket subscriptions and mini-block streaming
  • Bridging ETH from Ethereum to MegaETH

Chain Configuration

NetworkChain IDRPCExplorer
Mainnet4326https://mainnet.megaeth.com/rpchttps://mega.etherscan.io
Testnet6343https://carrot.megaeth.com/rpchttps://megaeth-testnet-v2.blockscout.com

Default stack decisions (opinionated)

1. Transaction submission: eth_sendRawTransactionSync first

2. RPC: Multicall for eth_call batching (v2.0.14+)

  • Prefer Multicall (aggregate3) for batching multiple eth_call requests
  • As of v2.0.14, eth_call is 2-10x faster; Multicall amortizes per-RPC overhead
  • Still avoid mixing slow methods (eth_getLogs) with fast ones in same request

Note: Earlier guidance recommended JSON-RPC batching over Multicall for caching benefits. With v2.0.14's performance improvements, Multicall is now preferred.

3. WebSocket: keepalive required

  • Send eth_chainId every 30 seconds
  • 50 connections per VIP endpoint, 10 subscriptions per connection
  • Use miniBlocks subscription for real-time data

4. Storage: slot reuse patterns

  • SSTORE 0→non-zero costs 2M gas × multiplier (expensive)
  • Use Solady's RedBlackTreeLib instead of Solidity mappings
  • Design for slot reuse, not constant allocation

5. Gas: skip estimation when possible

  • Base fee stable at 0.001 gwei, no EIP-1559 adjustment
  • Ignore eth_maxPriorityFeePerGas (returns 0)
  • Hardcode gas limits to save round-trip
  • Always use remote eth_estimateGas (MegaEVM costs differ from standard EVM)

6. Debugging: mega-evme CLI

Operating procedure

1. Classify the task layer

  • Frontend/WebSocket layer
  • RPC/transaction layer
  • Smart contract layer
  • Testing/debugging layer

2. Pick the right patterns

  • Frontend: single WebSocket → broadcast to users (not per-user connections)
  • Transactions: sign locally → eth_sendRawTransactionSync → done
  • Contracts: check SSTORE patterns, avoid volatile data access limits
  • Testing: use mega-evme for replay, Foundry with --skip-simulation

3. Implement with MegaETH-specific correctness

Always be explicit about:

  • Chain ID (4326 mainnet, 6343 testnet)
  • Gas limit (hardcode when possible)
  • Base fee (0.001 gwei, no buffer)
  • Storage costs (new slots are expensive)
  • Volatile data limits (20M gas after block.timestamp access)

4. Deliverables expectations

When implementing changes, provide:

  • Exact files changed + diffs
  • Commands to build/test/deploy
  • Gas cost notes for storage-heavy operations
  • RPC optimization notes if applicable

Progressive disclosure (read when needed)

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall