Base Skills
Official skills for the Base network: RPC endpoints, Foundry contract deploys, Builder Codes, AI agent registration and a node.
- 121 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Deploys and transactions on Base mainnet spend real ETH, and the agent works with the wallet key in a Foundry keystore.
- The `register.sh` script sends the wallet address to the external base.dev API.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/base-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Deploys and transactions on Base mainnet spend real ETH, and the agent works with the wallet key in a Foundry keystore.
- The `register.sh` script sends the wallet address to the external base.dev API.
This is third-party code. Review the repository files before installing.
What it does
Base Skills is the official skill set for building on the Base network. The `build-on-base` skill gathers everything into one playbook: RPC endpoints and chain IDs (8453 for mainnet, 84532 for Base Sepolia), Foundry contract deploys with BaseScan verification, testnet ETH from the CDP faucet, Builder Codes (the ERC-8021 attribution suffix for wagmi, viem and Privy) and running your own Reth node. The same skill covers registering an AI agent or trading bot: the `register.sh` script sends a wallet address to the base.dev API and prints the returned builder code. The second skill, `vibenet`, covers the Base Vibes devnet: native EIP-8130 accounts, ERC-8168 gas sponsorship and 200 ms blocks.
Who it is for. Developers of contracts and dapps on the Base network, plus authors of trading bots and AI agents who need transaction attribution.
Good fit when
- A contract has to be deployed to Base Sepolia with Foundry and verified on BaseScan.
- Transactions of a wagmi or viem dapp should carry a Builder Codes suffix so they earn referral fees.
- A trading bot needs a registered builder code to attribute its transactions.
- You are bringing up your own Base node on Reth and need hardware requirements and the sync procedure.
- A prototype on native EIP-8130 accounts with gas paid on behalf of the user is tested on the Vibenet devnet.
Not a fit when
- The project lives on another network: the addresses, chain IDs and tools in the skill are specific to Base.
- Contracts are written and deployed without Foundry: the skill covers that toolchain.
- You want to skip the testnet and go straight to mainnet.
Example request
Deploy this contract to Base Sepolia with Foundry, verify it on BaseScan and add the Builder Codes suffix to the transactions.Limitations
The skill gives instructions, the agent runs the commands, and a Base mainnet deploy spends real ETH. Foundry needs `forge` installed and a key in a keystore (`cast wallet import`), and private keys never go into the repository. The skill requires attaching a Builder Code to every transaction sent. `vibenet` relies on a viem fork with an `eip8130` module that the npm version lacks, while 200 ms blocks work in stock viem.
How to disable. Remove the `build-on-base` and `vibenet` folders from the agent skills directory. A registered builder code stays attached to the wallet, and Foundry keystore keys are removed separately.
FAQ
How do I install just the build-on-base skill?
Run `npx skills add base/skills --skill build-on-base`. The `npx skills add base/skills` command installs both skills of the repository.
Which networks does the skill cover?
Base mainnet with chain ID 8453 and the Base Sepolia testnet with chain ID 84532. The Vibenet devnet has its own `vibenet` skill.
What are Builder Codes?
An ERC-8021 attribution suffix appended to transactions. The skill wires it into wagmi, viem, Privy, ethers.js and `window.ethereum` so you can earn referral fees.
How do I register a trading bot or agent?
The `register.sh <wallet_address>` script sends the address to the base.dev API and prints the builder code it gets back. The agent then attaches it to transactions.
What is the vibenet skill for?
The Base Vibes devnet: native EIP-8130 accounts, session keys, ERC-8168 gas sponsorship and 200 ms blocks. Some of the code needs a viem fork that npm lacks.
Discussion
No questions or reviews yet.
Related
SkillsOfficial Base44 skills for agents: CLI, SDK, production troubleshooting and remote development in the cloud sandbox.
Corrections to what AI agents know about Ethereum: current gas, contract addresses, L2s, standards and smart contract security
NocoBase 3 skills guide an agent from an empty folder to a working business app: creation, plugins, upgrades and deployment.
The build-with-tinybase skill: the agent scaffolds and verifies local-first apps on the reactive TinyBase store
Nine skills for building on Chainlink: CRE, CCIP, Data Feeds, Data Streams, VRF and other network products
Builder Skills
Skills for agents
A set of small skills from Builder.io for agent work habits: visual plans and diff recaps, docs-first checks, cross-agent review and clean status updates
README in short
The README lists two recommended skills in a table with install commands and gives sample requests: connecting to mainnet, registering a bot with attribution, creating a smart account on Vibenet. Installation goes through the Skills CLI from skills.sh.
README badge
Original SKILL.md
--- 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) |