build-on-base — Claude Code skill: what it does, how to install
build-on-base guides smart contract deployment via Foundry, ERC-8021 transaction attribution, node operation, and agent setup on Base L2.
MIT 302 installs ★ 122 updated 2026-10-22
npx skills add base/skills --skill build-on-base -a claude-codeWhat build-on-base does
The skill equips your AI coding agent with instructions for building on the Base L2 network. It covers configuration for Base Mainnet (chain ID 8453) and Base Sepolia (84532), pairing Foundry deployment commands like forge create with BaseScan verification. The default stack relies on wagmi and viem for transactions.
Another core focus is Builder Codes under ERC-8021 using ox/erc8021. This attaches a dataSuffix to transactions in Wagmi, Viem, Privy, or ethers.js to track attribution and earn referral fees. The skill also documents bot and AI agent registration with the base.dev API, alongside instructions for running self-hosted Reth RPC nodes.
Sending transactions without attribution leads to silent data loss with zero warnings from the network. Because of this, the skill mandates Builder Codes on all outgoing calls and requires managing private keys via cast wallet import.
What it helps with
- Deploy and verify contracts on Base Sepolia or Mainnet using Foundry
- Add ERC-8021 Builder Code attribution to Viem or Wagmi transactions
- Register an automated trading bot or AI agent through the
base.dev API - Set up a self-hosted Base RPC node using Reth
Example prompts for the agent
- Deploy this contract to Base Sepolia using Foundry and verify on BaseScan
- Add an ERC-8021 builder code suffix to our Viem transaction client
- Give me the hardware specs and setup steps to run a self-hosted Base node with Reth
How to install build-on-base
1Skills CLI (Vercel)
npx skills add base/skills --skill build-on-base -a claude-code2Manually: put the files in place
~/.claude/skills/build-on-base/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/build-on-base/
1Skills CLI (Vercel)
npx skills add base/skills --skill build-on-base -a codex2Manually: put the files in place
.agents/skills/build-on-base/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add base/skills --skill build-on-base -a cursor2Manually: put the files in place
.cursor/skills/build-on-base/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install base/skills skills/build-on-base2Manually: put the files in place
.github/skills/build-on-base/SKILL.md1Skills CLI (Vercel)
npx skills add base/skills --skill build-on-base -a gemini-cli2Platform CLI
gemini skills install https://github.com/base/skills --path skills/build-on-baseManually: put the files in place
.devin/skills/build-on-base/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add base/skills --skill build-on-base -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about build-on-base
How to install build-on-base in Claude Code?
Run npx skills add base/skills --skill build-on-base -a claude-code. The playbook installs to ~/.claude/skills/build-on-base/SKILL.md.
What does build-on-base do?
It supplies your coding agent with playbooks for Base L2 development. It covers contract deployment, ERC-8021 transaction attribution, bot registration, and Reth node configuration.
How does the skill handle sensitive credentials?
The guardrails forbid committing raw private keys, requiring encrypted storage via cast wallet import. RPC keys and CDP credentials must always route through a backend proxy.
Source text
SKILL.md · MIT
--- name: build-on-base description: > Complete Base development playbook. Covers: (1) Network — Base RPC URLs, chain IDs (8453/84532), explorer config, testnet setup, connect to Base, Base Sepolia; (2) Contracts — Foundry deployment, forge create, BaseScan verification, CDP faucet, testnet ETH, deploy contract to Base; (3) Builder Codes — ERC-8021 attribution suffix, referral fees, dataSuffix for Wagmi/Viem/Privy/ ethers.js/window.ethereum, transaction attribution, earn referral fees, append builder code; (4) Agent registration — trading bots, AI agents, automated senders, ERC-8021 attribution wiring, base.dev API, register agent, builder code registration; (5) Node operation — run Base node, Reth setup, hardware requirements, self-hosted RPC, sync. --- # Base Development Complete playbook for building on Base L2 — network setup, smart contracts, developer tool attribution, agent registration, and node operation. ## Default Stack | Layer | Default | |-------|---------| | Network | Base Mainnet (8453) / Base Sepolia testnet (84532) | | Contracts | Foundry (`forge create` + BaseScan verification) | | Transactions | wagmi + viem | | Attribution | Builder Codes — ERC-8021 via `ox/erc8021` | | RPC (prod) | Dedicated node provider or self-hosted Reth | ## Safety Guardrails - **Never commit private keys** — use `cast wallet import` for Foundry keystores - **Never expose RPC API keys or CDP credentials client-side** — proxy through backend - **Never send transactions without Builder Code attribution** — silent data loss, no errors, no warnings - **Validate all user-provided shell inputs** before constructing forge/cast commands (no spaces, semicolons, pipes) ## Task Routing Read the reference for your task: | Task | When to Use | Reference | |------|-------------|-----------| | **Network config** | RPC URLs, chain IDs, explorer links, testnet setup | [references/network.md](references/network.md) | | **Deploy contracts** | Foundry deployment, BaseScan verification, faucet | [references/deploy-contracts.md](references/deploy-contracts.md) | | **Run a Base node** | Self-hosted RPC, Reth, hardware requirements | [references/run-node.md](references/run-node.md) | | **Builder Codes** | Add ERC-8021 attribution to transactions | [references/builder-codes/overview.md](references/builder-codes/overview.md) | | **Register AI agent/bot** | Register wallet, get builder code, wire attribution | [references/agents/register.md](references/agents/register.md) | ## Operating Procedure 1. **Classify the task** using the table above 2. **Read the relevant reference** before implementing 3. **Confirm the framework** with the user when multiple options exist (e.g., Privy vs wagmi for Builder Codes) 4. **Implement** with explicit chain ID, security requirements, and all required validations 5. **Deliver** diffs, install commands, and any manual steps (env vars, API key setup, wallet registration) ## For Edge Cases and Latest API Changes - **AI-optimized docs**: [docs.base.org/llms.txt](https://docs.base.org/llms.txt) - **Base chain docs**: [docs.base.org](https://docs.base.org) ## Installation ```bash npx skills add base/skills --skill build-on-base ```
© base · MIT · base/skills