Builder quickstart

Start here before the builder skill is installed. Use Node.js 22 or later and the exact release specified in your invitation. Keep the CLI and skill on the same release; copying only the entry file leaves its procedures unavailable.

1. Install the builder and its skill

Use Node.js 22 or later and install the exact invited release:

npm install -g @dvmkit/dvmctl@0.5.0-rc.3
npm install --ignore-scripts --prefix "$HOME/.dvmkit" @dvmkit/dvmctl@0.5.0-rc.3
dvmctl --version

Locate the installed skill directory:

skill_dir="$(dirname "$(NODE_PATH="$HOME/.dvmkit/node_modules" node -p "require.resolve('@dvmkit/dvmctl/skill')")")"

Copy the whole skill directory for your coding agent:

# Claude Code
mkdir -p "$HOME/.claude/skills/build-dvm"
cp -R "$skill_dir"/. "$HOME/.claude/skills/build-dvm/"

# Codex, for the current project
mkdir -p .agents/skills/build-dvm
cp -R "$skill_dir"/. .agents/skills/build-dvm/

Do not copy only SKILL.md. Its task procedures and payment recipes are part of the skill. For another harness, copy the same complete directory to its supported skill location.

2. Give your agent the canonical prompt

Help me build a DVM with dvmkit. Read the installed build-dvm skill. Establish one capability, its name, typed input, output, example, fiat price, and a separate test-payment cap. Reuse any decisions and approval I already supplied; ask only for material choices that are still missing. Then implement it, run dvmctl validate and dvmctl doctor, and test it locally. Use only the approved test rail and cap, with isolated caller state. Do not deploy, connect a production wallet, or use real funds without my separate approval.

A complete brief might say: “Build an uppercase service. It accepts { text: string }, returns the uppercase text as JSON, charges $0.01, and may spend at most $0.02 on one local Cashu test.” Your agent should ask only for missing choices.

3. Continue through the installed skill

The prompt above starts with one local capability. The skill then routes implementation, testing, deployment, operation, recovery, and retirement by task. An existing service can enter at the relevant task without repeating onboarding.

A local result proves handler behavior. A paid test also needs a terminal job, a verified receipt, and independent payment evidence. Deployment adds account access, hosting costs, payment destinations, and persistent state. Give the agent the intended scope and any existing authorization so it can continue without asking the same questions again.

Use Capabilities for the handler model, Payments and payouts for customer funds, and Deploying for hosting responsibilities. Exact commands live in the dvmctl reference.