mcpField
B
build-on-base

build-on-base

github.com/baseDevelopment120216 installsUpdated 1d ago
Repository

About build-on-base

build-on-base is a development skill with task-specific guidance for building on Base, from network setup and contract deployment to agent registration and node operation. It provides a default stack and security checks for implementation work.

Key features

  1. 01Base network configuration
  2. 02Foundry contract deployment
  3. 03Builder Codes attribution
  4. 04AI agent registration
  5. 05Base node operation
  6. 06Security guardrails

Use cases

  1. 01Configure Base Mainnet or testnet
  2. 02Deploy and verify contracts
  3. 03Add ERC-8021 transaction attribution
  4. 04Register an AI agent wallet

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/base/skills --skill build-on-base

After installing, type/build-on-basein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
deploy-contracts.md
network.md
run-node.md
references/agents/
register.md
references/builder-codes/
overview.md
privy.md
rpc.md
smart-wallets.md
viem.md
wagmi.md
scripts/
register.sh

Details

From the project README

Base Development

Complete playbook for building on Base L2 — network setup, smart contracts, developer tool attribution, agent registration, and node operation.

Default Stack

LayerDefault
NetworkBase Mainnet (8453) / Base Sepolia testnet (84532)
ContractsFoundry (forge create + BaseScan verification)
Transactionswagmi + viem
AttributionBuilder 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:

TaskWhen to UseReference
Network configRPC URLs, chain IDs, explorer links, testnet setupreferences/network.md
Deploy contractsFoundry deployment, BaseScan verification, faucetreferences/deploy-contracts.md
Run a Base nodeSelf-hosted RPC, Reth, hardware requirementsreferences/run-node.md
Builder CodesAdd ERC-8021 attribution to transactionsreferences/builder-codes/overview.md
Register AI agent/botRegister wallet, get builder code, wire attributionreferences/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

Installation

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

Comments

Markdown supported