ethskills

Name: ethskills
Availability: InStock
Author: Caelum

Correct Ethereum and L2 development misconceptions with gas and security guidance.

Updated Mar 21, 2026

Search Tags:#security #smart contracts #ethereum #defi #gas #l2 #verified addresses

Ready to run

npx skills add https://github.com/caelum0x/steelbot --skill ethskills-caelum0x

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ethskills
Source: https://github.com/caelum0x/steelbot/tree/main/skills/ethskills
Command: npx skills add https://github.com/caelum0x/steelbot --skill ethskills-caelum0x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill solves confusion and costly mistakes around Ethereum and L2 development by correcting common terminology, gas assumptions, standards, and security practices.

Core Features & Use Cases

Ethereum/L2 knowledge corrections: Establishes community conventions (e.g., “onchain”), updates gas and fee expectations, and compares L2 tradeoffs.
Verified address guidance: Provides vetted Base contract addresses and key integration endpoints to reduce misconfiguration errors.
DeFi + security reasoning patterns: Covers ERC standards, gasless transfer mechanics, oracle pitfalls, MEV risks, and safer token transfer practices.

Quick Start

Ask the agent: "Explain what gas costs and security mistakes to watch for when deploying and swapping USDC on Base, and list the verified Base addresses you should use."

Frequently Asked Questions about ethskills

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

FAQPage Schema

What are the most common Ethereum smart contract security mistakes to avoid when deploying on Base?▼

Common Ethereum smart contract security mistakes include incorrect gas budgeting, ignoring MEV risks, and using unverified addresses. Applying proper ERC-standard selection and verified contract identifiers on Base ensures onchain builds are accurate and safer against misconfiguration errors.

How do I estimate gas costs and fees for DeFi execution on Ethereum and L2 networks?▼

Estimating gas costs for DeFi execution on Ethereum and L2 networks requires updating outdated fee assumptions and comparing L2 tradeoffs. Correct gas budgeting accounts for oracle concerns, MEV risks, and gasless transfer mechanics to prevent costly transaction execution failures.

Which ERC standards should I select for safer token transfers in DeFi applications?▼

Selecting the correct ERC standards for DeFi token transfers involves evaluating gasless transfer mechanics and avoiding oracle pitfalls. Following established security best practices and conventions ensures safer token execution and reduces vulnerability exposure onchain.

Can I use unverified contract addresses when integrating USDC on Base, or do I need vetted endpoints?▼

Using unverified contract addresses for USDC on Base risks misconfiguration. You must use vetted Base contract addresses and key integration endpoints to ensure accurate onchain execution and reduce the chance of interacting with malicious or incorrect contracts.

What is the difference between Ethereum L1 and L2 development conventions for onchain builds?▼

The difference between Ethereum L1 and L2 development involves distinct gas expectations, fee structures, and layer tradeoffs. Correcting terminology to match community conventions like onchain and understanding L2 constraints ensures accurate deployment and safer contract execution.

When should I worry about MEV risks and oracle pitfalls during DeFi execution planning?▼

You should worry about MEV risks and oracle pitfalls during DeFi execution planning whenever contract deployment involves swapping tokens or reading external price feeds. Addressing these security concerns proactively prevents value extraction and data manipulation onchain.