ETHSKILLS skill

Corrections to what AI agents know about Ethereum: current gas, contract addresses, L2s, standards and smart contract security

  • 304 ★ on the repository
  • Last commit
Skill

Minimal access

Why this level

  • The skills are plain text and run or sign nothing themselves
  • When connected by link, the agent reads instructions from the external site ethskills.com
All reasons and checks

austintgriffith/ethskills

Install

Manual install

/plugin marketplace add austintgriffith/ethskills

Then run `/plugin install ethskills@ethskills`.

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • The skills are plain text and run or sign nothing themselves
  • When connected by link, the agent reads instructions from the external site ethskills.com

This is third-party code. Review the repository files before installing.

What it does

ETHSKILLS is a set of markdown skills that corrects the usual mistakes models make about Ethereum. The authors first test a stock model on a realistic task and keep in a skill only what it gets wrong: gas prices, token decimals, fork timelines, the state of L2s and contract addresses. The root holds the SKILL.md table of contents, with about twenty separate skills beside it: Ship (from idea to a deployed dApp), Gas and Costs, Wallets, Layer 2s, Standards, Security, Testing, Indexing, Frontend UX, QA, Audit and more. The agent loads only the ones it needs. Where skills touch keys and funds they carry safety rules, for example never committing private keys to Git. You can connect the set as a Claude Code plugin, by linking the root SKILL.md, or by giving the agent the URL of a single skill on ethskills.com.

Who it is for. Smart contract and dApp developers who write code with an agent and want to avoid stale gas prices and invented addresses.

Good fit when

  • An agent is writing a Solidity contract and has to remember reentrancy, token decimals and oracle manipulation
  • A dApp from scratch: the Ship skill advises starting with one or two contracts and picking a chain before the first line of code
  • The agent invents contract addresses and you need checked ones
  • Before deploying you need a security and QA checklist, including approve-button double fires
  • Choosing an L2: you need to check the current state of Base, Optimism and Polygon

Not a fit when

  • A project on Solana or another non-EVM chain: the skills cover Ethereum and its L2s
  • You need live chain data: the skills supply knowledge, and the EVM MCP Server in the catalog reads blocks and balances
  • You need today's gas or ETH quote: the skills store no prices and send the agent to `cast gas-price` and a live rate

Example request

Plan a tokenized ticketing dApp with the Ship skill, pick a chain and say how many contracts it needs

Limitations

Some claims are tied to dates, such as the shutdown of Polygon zkEVM in July 2026, and go stale as the network forks. If the agent loads a skill by link, it reads the text from ethskills.com each time, so it needs internet access. The plugin targets Claude Code; other agents rely on the SKILL.md link and the URLs of individual skills. Wallet operations run through the agent's own tools.

How to disable. For the plugin run `/plugin uninstall ethskills@ethskills` in Claude Code. If you pasted the SKILL.md link into an agent's context, remove it from the project instructions.

FAQ

How do I connect ETHSKILLS to Claude Code?

Run two commands: `/plugin marketplace add austintgriffith/ethskills` and `/plugin install ethskills@ethskills`. No clone is needed.

What if my agent cannot install plugins?

Ask it to install the skill from the link to the root SKILL.md in the repository. The agent reads the table of contents and then pulls in the skills it needs.

Why do the skills write onchain as one word?

The authors fixed it as an Ethereum community convention, while models habitually hyphenate it. The rule matters if the agent prepares documentation or publishable text.

How does new information get into a skill?

Every proposed change is triaged: a stock model gets a realistic task, and only a confirmed mistake goes into a skill. Pull requests are accepted from humans and agents.

Which skills should I start with?

For a new dApp open Ship, which points to the next phases. Security and QA help before deploying, and the architecture is worth running through CROPS Review.

Discussion

No questions or reviews yet.

Skills

A set of independent skills against drift in large codebases: hard-cut, root-cause tracing, lean testing and CI right-sizing.

SkillMinimal access140Repository stars

Brooklyn skills: 25 portable agent skills for pull requests, triage, cleanup, UI checks and research

SkillExtended access215Repository stars

Dozens of mizchi's agent skills: frontend audits, AWS, Cloudflare, SQL, Playwright and OpenTelemetry, installed one by one

SkillExtended access422Repository stars

24 skills for Laravel, PHP, React and TypeScript: code rules, testing, security, technical debt and documentation.

SkillMinimal access103Repository stars
Official

A skill for Claude Code and other agents: EasyEDA Pro API reference and a WebSocket bridge for debugging and extensions.

SkillExtended access1.1KRepository stars

A library of 30-plus instruction skills for coding agents: planning, building, testing, hallucination guards and shipping

SkillMinimal access217Repository stars

README in short

The README opens with the problem: models quote gas at 30 gwei and invent contract addresses. It then gives three ways to connect, the onchain spelling rule, a table of twenty skills with the typical model mistakes for each, a section on safety rules and a description of the verification method. It ends with links to the research repository and contribution rules.

README badge

Original SKILL.md

---
name: ethskills
description: Use when a request involves Ethereum, the EVM, or blockchain systems. Applies to building, auditing, deploying, or interacting with smart contracts, dApps, wallets, or DeFi protocols. Covers Solidity development, contract addresses, token standards (ERC-20, ERC-721, ERC-4626, etc.), Layer 2 networks (Base, Arbitrum, Optimism, zkSync, Polygon), and integrations with DeFi protocols such as Uniswap, Aave, and Curve. Includes topics such as gas costs, contract decimals, oracle safety, reentrancy, MEV, bridging, wallets, querying data from onchain, production deployment, and protocol evolution (EIP lifecycle, fork tracking, upcoming changes).
---

# ETHSKILLS — The missing knowledge between AI agents and production Ethereum.

You are probably wrong about Ethereum. Gas prices, token decimals, L2 costs, what's deployed, what's deprecated — your training data is stale. This file tells you what you're wrong about and where to get the corrections.

**Say "onchain" not "on-chain."** One word, no hyphen. Ethereum community convention.

---

## Start Here

**Building a dApp?** Fetch [ship/SKILL.md](https://ethskills.com/ship/SKILL.md) first. It plans the smallest shippable slice and points to other skills as each phase needs them.

**Need a specific topic?** Each skill below is standalone. Fetch only the ones relevant to your task.

**Base URL:** `https://ethskills.com/<skill>/SKILL.md`

---

## Skills

### [Why Ethereum](https://ethskills.com/why/SKILL.md)
Pectra/Fusaka upgrades, current network stats, the AI agent angle.
- Gas is under 1 gwei, not 10-30 gwei. 60-300x cheaper than your training data. Verify: `cast gas-price`
- ETH price is ~$2,000 (early 2026), not $2,500-3,000. Volatile — always verify.
- Pectra (May 2025) and Fusaka (Dec 2025) shipped. PeerDAS, 2x gas limit. EIP-7702 is live.
- ERC-8004 (onchain agent identity) and x402 (HTTP payments) exist and are production-ready.

### [Ship](https://ethskills.com/ship/SKILL.md) — Start here
End-to-end guide from idea to deployed dApp. Points to other skills as each phase needs them.
- Most dApps need 0-2 contracts, not 5-10. Three is the upper bound for an MVP.
- Solidity is for ownership, transfers, and commitments. Not a database, not a backend.
- Pick one chain for a concrete product fit (distribution, liquidity, AA, ecosystem). Measure fees live; never pick an L2 because "Ethereum is expensive."

### [CROPS Review](https://ethskills.com/crops/SKILL.md)
Deep CROPS architecture review against the EF Mandate values: Censorship Resistance, Open Source and Free (as in Freedom), Privacy, Security.
- Run for every dApp architecture plan and during pre-ship QA.
- Forces agents to label architecture options by CROPS impact instead of presenting neutral tradeoff lists.
- Output names the chosen default, accepted compromises, and the user's escape path.

### [Protocol](https://ethskills.com/protocol/SKILL.md)

Report a problem