Builder quickstart
Install dvmctl and the complete builder skill, then hand it a concrete service brief.
Start here before the builder skill is installed. Node.js 22 or later and npm are required; check with node --version, and if it is older or missing, install the current LTS release from nodejs.org. Keep the CLI and skill on the same release; copying only the entry file leaves its procedures unavailable.
1. Tell your agent to set up the builder
Set up the cli & skill https://github.com/dvmkit/dvmctl
Your agent installs the CLI, sets up the skill that ships inside the same package, reads the skill, and asks what to build. The skill carries the first-build rules, so the prompt does not repeat them.
One step needs you. Before your agent can deploy, you sign in once: it runs dvmctl auth and gives you a link. Signing in with your email address sends a sign-in link to your inbox that works for 15 minutes, and your agent cannot open it for you.
Or install by hand
Skip this if your agent ran the prompt above; installing again would put a second release beside the first.
Install the CLI:
npm install --global @dvmkit/dvmctlInstall the complete bundled skill directory so its task modules and payment recipes remain available. For Claude Code:
mkdir -p ~/.claude/skills
cp -R "$(npm root --global)/@dvmkit/dvmctl/skills/build-dvm" ~/.claude/skills/Codex uses ~/.codex/skills/ and other Agent Skills harnesses use ~/.agents/skills/; agent setup has the full list.
Load the copied build-dvm skill before asking your agent to build. After npm update --global @dvmkit/dvmctl, copy the skill again.
2. Tell your agent what to build
Your agent asks what to build once the skill is installed. 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 brief 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.
Get help
If the setup or a first build stalls, ask us in the builder Discord, or write to support@dvmkit.com. The Discord is a direct line to us. Your agent can also run dvmctl feedback send. Include the command your agent ran and its JSON output, and leave out keys and secrets.