Skills

Skill 3 of 5

Build On Base

Complete Base development playbook.

1 minute · 244 words · 7 sections

Install

$ npx skills add base/skills --skill build-on-base

$ npx skills add base/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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 (opens in a new tab)
Deploy contracts	Foundry deployment, BaseScan verification, faucet	references/deploy-contracts.md (opens in a new tab)
Run a Base node	Self-hosted RPC, Reth, hardware requirements	references/run-node.md (opens in a new tab)
Builder Codes	Add ERC-8021 attribution to transactions	references/builder-codes/overview.md (opens in a new tab)
Register AI agent/bot	Register wallet, get builder code, wire attribution	references/agents/register.md (opens in a new tab)

Operating Procedure

Classify the task using the table above
Read the relevant reference before implementing
Confirm the framework with the user when multiple options exist (e.g., Privy vs wagmi for Builder Codes)
Implement with explicit chain ID, security requirements, and all required validations
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 (opens in a new tab)
Base chain docs: docs.base.org (opens in a new tab)

Installation

npx skills add base/skills --skill build-on-base

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/base/skills, branch master, last pushed 17 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

5 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .claude/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

1 of 5 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “7 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /base/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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 (opens in a new tab)
Deploy contracts	Foundry deployment, BaseScan verification, faucet	references/deploy-contracts.md (opens in a new tab)
Run a Base node	Self-hosted RPC, Reth, hardware requirements	references/run-node.md (opens in a new tab)
Builder Codes	Add ERC-8021 attribution to transactions	references/builder-codes/overview.md (opens in a new tab)
Register AI agent/bot	Register wallet, get builder code, wire attribution	references/agents/register.md (opens in a new tab)

Operating Procedure

Classify the task using the table above
Read the relevant reference before implementing
Confirm the framework with the user when multiple options exist (e.g., Privy vs wagmi for Builder Codes)
Implement with explicit chain ID, security requirements, and all required validations
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 (opens in a new tab)
Base chain docs: docs.base.org (opens in a new tab)

Installation

npx skills add base/skills --skill build-on-base

Build On Base

Base Development

Default Stack

Safety Guardrails

Task Routing

Operating Procedure

For Edge Cases and Latest API Changes

Installation

About this skill

Trigger

Colophon

Build On Base

Base Development

Default Stack

Safety Guardrails

Task Routing

Operating Procedure

For Edge Cases and Latest API Changes

Installation

Appendix 3.1–3.11

ReferencesMarkdown · 10 files

ScriptsShell · 1 file

About this skill

Trigger

Colophon

Appendix 3.1–3.11

ReferencesMarkdown · 10 files

ScriptsShell · 1 file