Skip to main content

​
Overview

The Brickken Skill is an AI-agent skill built on the open Agent Skills format (SKILL.md). It works with any agent that supports the standard — including Claude Code, OpenAI Codex, Gemini CLI, Cursor, and GitHub Copilot — and helps agents choose and use the right Brickken surface:
  • Dapp API when you have a Brickken API key.
  • Agentic API when you do not have an API key and want to use private-key based x402 flows.
  • MCP when your agent can connect to the hosted Brickken MCP server.
  • CLI when local signing and terminal execution are the best fit.
Use the skill when an agent needs to inspect Brickken endpoints, prepare request bodies, understand expected responses, or decide whether a task should go through the API, CLI, or MCP.

Download Skill

Download the standalone Brickken skill archive.

CLI package

Install the public brickken-cli package from npm.

GitHub repository

View the public CLI and bundled skill source.

MCP

Open the official Brickken MCP page.

​
Install Only the Skill

Use this path when you want the Brickken Skill without installing the CLI globally. Download the archive and unzip it into your agent’s skills directory:
AgentPersonal skills directory
Claude Code~/.claude/skills
OpenAI Codex~/.codex/skills
Gemini CLI~/.gemini/skills
Cursor~/.cursor/skills
GitHub Copilot / VS Code~/.copilot/skills
Other agentsSee your agent’s documentation for its skills directory
export SKILLS_DIR=~/.claude/skills   # set to your agent's skills directory

mkdir -p "$SKILLS_DIR"
curl -L https://raw.githubusercontent.com/fbrickken/docs/main/downloads/brickken-skill.zip -o /tmp/brickken-skill.zip
rm -rf "$SKILLS_DIR/brickken"
unzip -o /tmp/brickken-skill.zip -d "$SKILLS_DIR"
Verify the installation: 
test -f "$SKILLS_DIR/brickken/SKILL.md" && echo "Brickken skill installed"
Most agents also discover project-level skills from a directory inside the repository (for example .claude/skills, .cursor/skills, .gemini/skills, or .github/skills). Unzip the archive there instead to share the skill with your team through version control. Start a new agent session after installing the skill so the agent reloads its available skills.

​
Install with the CLI

If you already use the Brickken CLI, install the bundled skill with: 
npm install -g brickken-cli
brickken skill install
By default the installer targets ~/.codex/skills. Pass --path to install into any other agent’s skills directory: 
brickken skill install --path ~/.claude/skills --force
To install without a global CLI install, run the installer through npx: 
npx brickken-cli skill install --path ~/.claude/skills --force
Inspect where the npm package bundles the skill: 
brickken skill path

​
Configure Credentials

​
Dapp API

Use the Dapp API when you have a Brickken API key. 
export BRICKKEN_API_KEY="YOUR_BRICKKEN_API_KEY"
The skill guides the agent toward API-key authenticated endpoints, request bodies, response examples, and transaction preparation or send flows.

​
Agentic API

Use the Agentic API when you want private-key based x402 flows without a Brickken API key. 
export BRICKKEN_PRIVATE_KEY="0xYOUR_PRIVATE_KEY"
export BRICKKEN_RPC_URL="https://ethereum-sepolia-rpc.publicnode.com"
The private key is used by your local agent runtime, CLI, or trusted MCP session for x402 payment signing and blockchain transaction signing. Never send a private key to the Brickken API.
Do not paste production API keys or private keys into shared chats, tickets, terminals, or logs. Use your agent client’s secret store or local environment variables.

​
Example Prompts

Use the Brickken skill to prepare a new tokenization with my Dapp API key.

Use the Brickken skill to register an ERC-8004 agent with the Agentic API and no API key.

Use the Brickken skill to decide whether this workflow should use the API, CLI, or MCP.