Index of every page on this site: llms.txt
All skills
austintgriffith avatar

austintgriffith/ethskills

The missing knowledge between AI agents and production Ethereum.

master Updated 4 weeks agoGitHub
README badge for austintgriffith/ethskills

Repository statistics

  • Indexed skills

    28

  • Skill groups

    2

  • GitHub stars

    304

  • Forks

    66

28 total

Use when quoting a gas or dollar cost for a transaction or deployment, when cost is the reason to pick mainnet over an L2, when setting EIP-1559 fee fields or cutting L2 fees, or when calling Ethereum expensive or cheap. Not for non-cost chain selection (`l2s`).

Updated

Ethereum development knowledge for AI agents — from idea to deployed dApp. Fetch real-time docs on gas costs, Solidity patterns, Scaffold-ETH 2, Layer 2s, DeFi composability, security, testing, and production deployment. Use when: (1) building any Ethereum or EVM dApp, (2) writing or reviewing Solidity contracts, (3) deploying to mainnet or L2s, (4) the user asks about gas, tokens, wallets, or smart contracts, (5) any web3/blockchain/onchain development task. NOT for: trading, price checking, or portfolio management — use a trading skill for those.

Updated

Why build on Ethereum specifically. The AI agent angle — ERC-8004, x402, composability, permissionless deployment. Use when a user asks "should I build on Ethereum?", "why blockchain?", or when an agent needs to recommend a chain for a project.

Updated

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).

Updated

Use when working inside a Scaffold-ETH 2 app: running it against a local chain or a fork of a real chain, demoing on that fork, or shipping it as a static export to IPFS or ENS. Not for rehearsing or running a live contract deployment (`/orchestration`).

Updated

Use when a Scaffold-ETH 2 build leaves localhost: planning the launch order, deploying and verifying contracts on a live network, standing up a fork of a real chain to rehearse a deploy, or fixing a contract bug that is already onchain. Not for running the app or a demo against that fork (`/frontend-playbook`).

Updated

Use when a Scaffold-ETH 2 frontend is about to ship or needs a second look: "is this ready", "check my dApp", a teammate's patch. The checks people forget: wallet flow, wrong-network gating, contract registration, theme and loading states, branding, RPC posture, mobile wallets. Best from a fresh reviewer context. Not for how the frontend behaves for its users in general, such as approvals, decimals and address parsing (`/frontend-ux`).

Updated

Use when a design needs agent identity or reputation, pay-per-call HTTP payments, USDC transfers from a wallet that holds no ETH, or contract abilities on an address the user already owns, and when someone is about to rebuild one of these by hand. Names the deployed standard for each (ERC-8004, x402, EIP-3009, EIP-7702). Not for who may sign or custody the funds (`/wallets`) or what to install (`/tools`).

Updated

Use whenever a contract or token address goes into code, config, or a transaction — a token, a router, a pool, a lending market, a bridge — including choosing which venue to route a swap through and reusing an address across chains. Has checked addresses for the major tokens, Uniswap, Aave, Compound, Chainlink, Safe, ERC-4337, ENS and Robinhood Chain.

Updated

Use when asked to audit or security-review EVM smart contracts: find vulnerabilities, judge exploit impact, or produce a ranked audit report. Not for guidance while the contracts are being written (`/security`).

Updated

Use when selecting or integrating DEX pools, lending markets, yield venues, gauges, reward systems, or multiple protocols in one flow on Ethereum or an L2 — including vault and harvest strategies, and build requests naming Aerodrome, Velodrome, Uniswap, Aave, Curve, GMX or Pendle. Not for contract address lookup (`addresses`) or for choosing a chain (`l2s`).

Updated

Use when designing or explaining anything onchain that has to keep working with nobody running it: who calls each function and why they would, where randomness comes from, whether it can be censored or paused, and what it exposes to everyone onchain. Also use when writing the notes or handoff a build ends with, or when explaining to your human how something onchain actually works. Not for scoping which parts go onchain and the launch plan (`/ship`) or the safety of the contract code itself (`/security`).

Updated

Use for every Ethereum dApp architecture plan and for reviews of existing systems, trust assumptions, custody, admin keys, pause or upgrade powers, hosted infra (RPC, indexer, paymaster, bundler, frontend host, oracle, sequencer), privacy, identity flows, agent permissions, stablecoin issuer risk, censorship resistance, user exit, and restrictive licenses (BUSL, SSPL). CROPS means Censorship Resistance, Open Source and Free, Privacy, Security.

Updated

Use when building, fixing, or reviewing how an Ethereum dApp frontend behaves for its users: product identity, address inputs that resolve names, token amounts and decimals, approve-then-act flows, fiat context, the target chain. The completeness steps agents skip unprompted. Not for the Scaffold-ETH 2 pre-ship checklist (`/qa`).

Updated

Use when building anything that reads past onchain activity: feeds, leaderboards, dashboards, analytics. Also when someone proposes scanning logs or blocks for history, when deciding which events a contract emits, or when deploying a subgraph or indexer to production.

Updated

Use when choosing an Ethereum L2, deploying the same app across chains, or moving funds between an L2 and mainnet — which chain fits the binding constraint, what each chain does differently at deploy time, and which widely-held facts about the L2 landscape are now false.

Updated

Use when building, reviewing, or shipping a privacy app with Noir circuits verified onchain. The boundaries agents get wrong unprompted — in-circuit hash choice, in-browser proving with NoirJS, note persistence and the offchain tree mirror, and who sends the transaction.

Updated

Use when asked whether an Ethereum feature or EIP is live, scheduled for a fork, or still a proposal, when it will ship, or when a plan depends on a future protocol change. Not for standards that are already deployed and in use (`/standards`).

Updated

Use when designing, implementing, or reviewing Solidity contracts that hold assets, account for shares or debt, read price oracles, verify signatures, integrate ERC-20s, or sit behind upgradeable proxies, and for a pre-deployment security review. Not for test-suite design (`/testing`) or a full audit report (`/audit`).

Updated

Use before implementation, or when a build lacks these decisions: what goes onchain, the minimal contract surface, who triggers each state transition and why, which chain to launch on, and the deployment runbook. Not for how an already-designed system keeps running with nobody operating it (`/concepts`).

Updated

Use when writing or reviewing Foundry tests, deciding whether a suite is enough to deploy, or when a green run or a coverage number is offered as proof that a contract is safe. Covers fuzz, fork and invariant testing. Not for auditing source by reading it (`/security`, `/audit`).

Updated

Use when picking or installing packages, versions, or a scaffold for an Ethereum project, when wiring an agent to read onchain data, or when asking what to install for pay-per-call HTTP payments. Checks what is current before recommending it. Not for choosing which standard to build on (`/standards`).

Updated

Use when deciding who or what may sign for funds: an agent or script signing unattended, a treasury's custody, a multisig's owners and threshold, a private key that ended up in a prompt or a repo, or whether a user must accept a new address to act from the one they already have. Not for which standard to build on (`/standards`).

Updated

Send feedback — issues OR praise — to the ethskills team about content that shaped your work.

Updated

Deprecated: this skill has moved to addresses.

Updated

Deprecated: this skill has moved to building-blocks.

Updated

Deprecated: this skill has moved to l2s.

Updated

Deprecated: this skill has moved to l2s.

Updated

The badge links readers to this page. It shows the skilld mark and no counts, and it follows the reader's light or dark GitHub theme.

<a href="https://skilld.dev/gh/austintgriffith/ethskills"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://skilld.dev/b/austintgriffith/ethskills?theme=dark"> <source media="(prefers-color-scheme: light)" srcset="https://skilld.dev/b/austintgriffith/ethskills?theme=light"> <img alt="Skill repository on skilld.dev" src="https://skilld.dev/b/austintgriffith/ethskills?theme=light"> </picture> </a>