FlowCraft Config Authoring
GizClaw/flowcraft
Writes and validates a complete FlowCraft agent deployment: deploy.yaml, runtime settings, resource sub-documents and graph JSON, checked against a structural validator.
Complete Base development playbook. An agent skill from base/skills.
Install Build On Base
$ npx skills add base/skills --skill build-on-base -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install base/skills build-on-base --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/base/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/build-on-base .claude/skills/build-on-base && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "build-on-base" agent skill from https://github.com/base/skills/tree/master/skills/build-on-base into .claude/skills/build-on-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-on-base", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/base/skills/tree/master/skills/build-on-baseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add base/skills --skill build-on-base -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install base/skills build-on-base --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/base/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/build-on-base .agents/skills/build-on-base && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "build-on-base" agent skill from https://github.com/base/skills/tree/master/skills/build-on-base into .agents/skills/build-on-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-on-base", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add base/skills --skill build-on-base -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install base/skills build-on-base --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/base/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/build-on-base .cursor/skills/build-on-base && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "build-on-base" agent skill from https://github.com/base/skills/tree/master/skills/build-on-base into .cursor/skills/build-on-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-on-base", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/base/skills.git --path skills/build-on-base--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add base/skills --skill build-on-base -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install base/skills build-on-base --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/base/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/build-on-base .gemini/skills/build-on-base && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "build-on-base" agent skill from https://github.com/base/skills/tree/master/skills/build-on-base into .gemini/skills/build-on-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-on-base", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install base/skills build-on-baseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add base/skills --skill build-on-base -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/base/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/build-on-base .github/skills/build-on-base && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "build-on-base" agent skill from https://github.com/base/skills/tree/master/skills/build-on-base into .github/skills/build-on-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-on-base", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add base/skills --skill build-on-base -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install base/skills build-on-base --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/base/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/build-on-base .opencode/skills/build-on-base && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "build-on-base" agent skill from https://github.com/base/skills/tree/master/skills/build-on-base into .opencode/skills/build-on-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-on-base", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
build-on-base- GitHub stars
- 121
- Token cost
- ~804 tokens
- SKILL.md length
- 247 words
- Files
- 12 (incl. scripts, references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Complete Base development playbook. An agent skill from base/skills.
- Works in 5 steps: Classify the task using the table above → Read the relevant reference before… → Confirm the framework with the user when… → …
- Tasks that involve Building AI agents
- SKILL.md covers Default Stack, Safety Guardrails, Task Routing and Operating Procedure, plus 2 more sections
- Runs Shell scripts from its folder; calls npx
What it does
Build On Base is an agent skill from base/skills. 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…
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts and reference files (for example `references/agents/register.md`, `references/builder-codes/overview.md` and `references/builder-codes/privy.md`).
It sits in AI & LLM Engineering, covering Building AI agents, Trading and backtesting and Deployment. It works with viem and wagmi and Ethereum. The repository describes itself as: npx skills add base/skills. The licence is MIT.
When your agent uses it
- Tasks that involve Building AI agents
- Tasks that involve Trading and backtesting
- Tasks that involve Deployment
Example prompts
- “/build-on-base”
Requirements
- Node.js
- A Bash shell
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 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)
What it can do on your machine
Read from SKILL.md and the folder at commit 4f3d8f3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.base.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Build On Base loads about 804 tokens when it runs, and up to ~8.7k if it reads all its reference files. Until then it costs about 184 tokens; SKILL.md has 247 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from base/skills at commit 4f3d8f3, republished under its MIT licence (© base). 247 words, ~804 tokens.
Download SKILL.mdSave it as
.claude/skills/build-on-base/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- 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 importfor 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 |
| 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 |
| Register AI agent/bot | Register wallet, get builder code, wire attribution | references/agents/register.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 chain docs: docs.base.org
Installation
npx skills add base/skills --skill build-on-base© base, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files (scripts, references) in skills/build-on-base of base/skills.
- SKILL.md
- references/agents/register.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/network.md
- references/run-node.md
- scripts/register.sh
Open the folder on GitHubat commit 4f3d8f3
Compare with similar skills
Build On Base next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Build On Base this skillbase/skills | 121 | — | ~804 | Automated safety check: Pass | MIT | |
| FlowCraft Config AuthoringGizClaw/flowcraft | 416 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Microsoft Foundrymicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~6.7k | Automated safety check: Pass | MIT | |
| Deploy AI Agentbolivian-peru/os-moda | 118 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Langsmith Deploymentsoba-labs/langchain-agent-skills | 107 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Ak Inityaalalabs/agent-kernel | 191 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Microsoft Foundry
microsoft/GitHub-Copilot-for-Azure
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end.
Deploy AI Agent
bolivian-peru/os-moda
Deploy and manage AI agent workloads with GPU checks, API key management, and health monitoring
Langsmith Deployment
soba-labs/langchain-agent-skills
Deploy and operate production agent servers with LangSmith Deployment.
Ak Init
yaalalabs/agent-kernel
Scaffold a new Agent Kernel project from scratch. An agent skill from yaalalabs/agent-kernel.
Google Agents CLI Adk Code
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management", or needs ADK (Agent…
More from base/skills
Vibenet
base/skills
Build on vibenet — Base's devnet for native account abstraction (EIP-8130), payer gas sponsorship (ERC-8168), and Cobalt 200ms native blocks.
Plugin Review
base/skills
Validate and review Base MCP plugin files against the Plugin Specification.
Base MCP
base/skills
Base MCP — gives your AI assistant access to a Base Account via the Base MCP server (wallet-mcp.coinbase.com).
Related
Works with
Questions about Build On Base
What does Build On Base do?
Complete Base development playbook. An agent skill from base/skills. Build On Base is an agent skill from base/skills. Complete Base development playbook.
When should I use Build On Base?
Build On Base fits situations like: tasks that involve Building AI agents; tasks that involve Trading and backtesting; tasks that involve Deployment.
How do I install Build On Base in Claude Code?
Run `npx skills add base/skills --skill build-on-base -a claude-code`. Or copy the skill folder (skills/build-on-base in base/skills) into .claude/skills/build-on-base in your project. Claude Code loads it when a task matches its description.
How do I install Build On Base in Codex?
Run `npx skills add base/skills --skill build-on-base -a codex`. Or copy the skill folder (skills/build-on-base in base/skills) into .agents/skills/build-on-base in your project. Codex loads it when a task matches its description.
Can I use Build On Base in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add base/skills --skill build-on-base -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-on-base, .gemini/skills/build-on-base, .github/skills/build-on-base and .opencode/skills/build-on-base in your project.
What does Build On Base need to run?
Going by SKILL.md and its folder, Build On Base needs a shell for the scripts in its folder and the command-line tools its instructions call (npx). Our summary lists: Node.js; A Bash shell.
Does Build On Base access the network?
SKILL.md names 1 domain. As links in the text: docs.base.org. This is read from the text; nothing was executed.
Is Build On Base safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Build On Base use?
Build On Base is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Build On Base use?
About 804 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.9k tokens, read only when the agent opens those files.
What are the alternatives to Build On Base?
Skills that share tags, products or a category with Build On Base: FlowCraft Config Authoring (GizClaw/flowcraft, 416 stars), Microsoft Foundry (microsoft/GitHub-Copilot-for-Azure, 255 stars), Deploy AI Agent (bolivian-peru/os-moda, 118 stars) and Langsmith Deployment (soba-labs/langchain-agent-skills, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Build On Base?
base (a GitHub organization) maintains it in base/skills, which has 121 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 1, 2026.
Source: base/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.