Build On Base Agent Skill

> 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) Base Account SDK — Sign in with Base (SIWB), Base Pay, USDC payments, paymasters, gas sponsorship, sub-accounts, spend permissions, prolinks, batch transactions, smart wallet, payment link, recurring subscription; (5) Agent registration — trading bots, AI agents, automated senders, ERC-8021 attribution wiring, base.dev API, register agent, builder code registration; (6) Node operation — run Base node, Reth setup, hardware requirements, self-hosted RPC, sync; (7) Migrations — migrate OnchainKit, OnchainKitProvider to WagmiProvider, wagmi migration, remove onchainkit dependency, MiniKit to Farcaster SDK, convert miniapp, Farcaster miniapp to regular app, convert Farcaster miniapp.

53k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

104

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

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

What comes with it

205 171 bytes besides the instruction

references/agents/register.md

references/base-account/authentication.md

references/base-account/capabilities.md

references/base-account/overview.md

references/base-account/payments.md

references/base-account/prolinks.md

references/base-account/sub-accounts.md

references/base-account/subscriptions.md

references/base-account/troubleshooting.md

references/builder-codes/overview.md

references/builder-codes/privy.md

references/builder-codes/rpc.md

references/builder-codes/smart-wallets.md

references/builder-codes/viem.md

references/builder-codes/wagmi.md

references/deploy-contracts.md

references/migrations/farcaster-miniapp-to-app.md

references/migrations/minikit-to-farcaster/auth.md

references/migrations/minikit-to-farcaster/dependencies.md

references/migrations/minikit-to-farcaster/examples.md

references/migrations/minikit-to-farcaster/manifest.md

references/migrations/minikit-to-farcaster/mapping.md

references/migrations/minikit-to-farcaster/overview.md

references/migrations/minikit-to-farcaster/pitfalls.md

references/migrations/minikit-to-farcaster/provider.md

references/migrations/onchainkit/overview.md

references/migrations/onchainkit/provider.md

references/migrations/onchainkit/transaction.md

references/migrations/onchainkit/troubleshooting.md

references/migrations/onchainkit/wallet.md

references/network.md

references/run-node.md

scripts/analyze_project.py

scripts/register.sh

scripts/validate_conversion.py

The instruction itself

7 sections, as written by the author

Base Development

Complete playbook for building on Base L2 — network setup, smart contracts, wallet auth, payments,

developer tool attribution, and framework migrations.

Default Stack

| Layer | Default |

|-------|---------|

| Network | Base Mainnet (8453) / Base Sepolia testnet (84532) |

| Contracts | Foundry (forge create + BaseScan verification) |

| Wallet auth | Base Account SDK (@base-org/account) |

| Payments | Base Pay — USDC, gasless, settles in <2s |

| 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 skip server-side payment verification — always call getPaymentStatus() server-side and verify sender, amount, recipient; track processed tx IDs to prevent replay attacks
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)
COOP headers for Base Account popups — use same-origin-allow-popups, not same-origin

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 |

| Deploy contracts | Foundry deployment, BaseScan verification, faucet | references/deploy-contracts.md |

| Run a Base node | Self-hosted RPC, Reth, hardware requirements | references/run-node.md |

| Builder Codes | Add ERC-8021 attribution to transactions | references/builder-codes/overview.md |

| Base Account SDK | SIWB, Base Pay, subscriptions, sub-accounts | references/base-account/overview.md |

| Register AI agent/bot | Register wallet, get builder code, wire attribution | references/agents/register.md |

| Migrate from OnchainKit | OnchainKitProvider → wagmi, wallet/tx components | references/migrations/onchainkit/overview.md |

| MiniKit → Farcaster SDK | @coinbase/onchainkit/minikit → @farcaster/miniapp-sdk | references/migrations/minikit-to-farcaster/overview.md |

| Farcaster miniapp → regular app | Remove Mini App host coupling, convert to Base/web app | references/migrations/farcaster-miniapp-to-app.md |

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
Base Account reference: docs.base.org/base-account
Base chain docs: docs.base.org

Installation

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

Other skills for the same job

different authors, same section of the catalogue

Edgartools

by christophacham

×2

Python library for accessing, analyzing, and extracting data from SEC EDGAR filings. Use when working with SEC filings, financial statements (income statement, balance sheet, cash flow), XBRL financial data, insider trading (Form 4), institutional holdings (13F), company financials, annual/quarterly reports (10-K, 10-Q), proxy statements (DEF 14A), 8-K current events, company screening by ticker/CIK/industry, multi-period financial analysis, or any SEC regulatory filings.

15k tokens

Altllm Portal API Keys

by internet-court

×1

Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.

Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.

Use this umbrella skill when the request spans multiple AltLLM Portal CLI domains, or when you need to navigate the local altllm CLI in this repository across auth, API keys, billing history, NOWPayments payment links, and related x402 Portal top-up guidance.

Build with the ChainGPT Web3 AI developer platform. Full API/SDK reference and project scaffolding for: Web3 AI Chatbot & LLM, AI NFT Generator, Smart Contract Generator, Smart Contract Auditor, AI Crypto News, AgenticOS Twitter agents, and Solidity LLM. Use when building blockchain apps, Web3 chatbots, NFT tools, smart contract tools, crypto news feeds, AI agents, or integrating any ChainGPT API. Triggers: chaingpt, web3 ai, nft generator, smart contract audit, crypto news api, agenticos, solidity llm, cgpt, blockchain ai, token analytics.

TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.

>- Guide for developing with near-api-js v7 - the JavaScript/TypeScript library for NEAR blockchain interaction. (3) calling smart contracts, (4) managing accounts and keys, (5) working with NEAR RPC API, (6) handling FT/NFT tokens on NEAR, (7) using NEAR cryptographic operations (KeyPair, signing), (8) converting between NEAR units (yocto, gas), (9) gasless/meta transactions with relayers, (10) NEP-413 message signing for authentication, (11) storage deposit management for FT contracts. Triggers on any NEAR blockchain development tasks.

TypeScript library for NEAR Protocol blockchain interaction. Use this skill when writing code that interacts with NEAR Protocol, including viewing contract data, calling contract methods, sending NEAR tokens, building transactions, creating type-safe contract wrappers, integrating wallets (Wallet Selector, HOT Connect), React hooks and providers (@near-kit/react), managing keys, testing with sandbox, meta-transactions (NEP-366), and message signing (NEP-413).

8k tokens

How to use it

Copy the folder

Take base/build-on-base from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.