Skills
Email & Tools Official

Vercel Deployments

Give NanoClaw agents the ability to deploy web applications to Vercel. Installs the Vercel CLI in agent containers.

What it does

  • Agents can deploy projects to Vercel from inside the container
  • Vercel CLI baked into the container image
  • OneCLI-managed Vercel API token — no raw credentials in containers
  • Container-side skill (vercel-cli) loaded automatically
  • Works for personal projects and team accounts

What you'll need

  • NanoClaw installed and running
  • OneCLI Agent Vault initialized (run /init-onecli first)
  • A Vercel account with a personal access token

Install

/add-vercel

How it works

The /add-vercel skill gives NanoClaw agents the ability to ship web apps to Vercel. It installs the vercel CLI in the container image, copies a container-side skill that documents the right flags, and registers a Vercel API token with OneCLI so credentials are injected at request time without ever entering the container.

Once installed, you can ask the agent to deploy a project, list deployments, manage domains, or run any other Vercel CLI operation — the agent handles the commands inside its sandbox.

Setup

The skill is mostly automated. It walks through five phases:

  1. Pre-flight — checks OneCLI is initialized.
  2. Install container skill — copies the bundled vercel-cli container skill into container/skills/.
  3. Configure credentials — asks for your Vercel personal access token, registers it with OneCLI under host pattern api.vercel.com, and assigns it to all existing agents.
  4. Add to container image — adds vercel to the container’s global npm install if not already present, then rebuilds.
  5. Sync to running groups — copies the new container skill into existing agent groups so they pick it up on next wake.

Get a Vercel token from vercel.com/account/tokens. Use Full Account scope (the agent needs to create projects, deploy, and manage domains) and a long expiration to avoid frequent rotation.

What you get

The agent can run:

  • vercel deploy --yes --prod — production deployment
  • vercel ls — list deployments
  • vercel whoami — check auth
  • vercel domains add / vercel alias — domain management
  • Any other Vercel CLI command

The container-side vercel-cli skill is loaded automatically with each agent invocation, so the model knows what flags to pass.

Tips

  • OneCLI’s selective secret mode is per-agent. The skill auto-assigns the Vercel secret to every existing agent at install time, but you’ll need to re-assign it manually for any agents created later.
  • Tokens with No expiration are easiest. If your security policy requires expiry, set a calendar reminder before the rotation date.
  • The agent uses the --token placeholder flag. The literal “placeholder” string is replaced by OneCLI’s gateway with the real token at request time — that’s why containers can run Vercel commands without ever seeing the credential.
  • Test deployment with a tiny project first. The agent can scaffold a Next.js app, push it to Vercel, and return the live URL within a minute.