add-vercel

Installs the Vercel CLI in NanoClaw agent containers and configures OneCLI credential injection for api.vercel.com.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/RADHA0-max/selfhealbackend --skill add-vercel-radha0-max
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-vercel
Source: https://github.com/RADHA0-max/selfhealbackend/tree/main/nanoclaw/.claude/skills/add-vercel
Command: npx skills add https://github.com/RADHA0-max/selfhealbackend --skill add-vercel-radha0-max

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vitest.

What problem does it solve? NanoClaw agents cannot deploy web applications to Vercel out of the box — they lack the Vercel CLI in their container image and have no secure way to authenticate with the Vercel API. This Skill performs the full installation and credential wiring so agents can deploy immediately. ## Core Features & Use Cases - Container Skill Installation: Copies a bundled vercel-cli skill into the container skills directory and syncs it to all running agent group sessions. - Credential Injection via OneCLI: Registers a Vercel personal access token as a OneCLI secret scoped to api.vercel.com and assigns it to every agent, so the proxy injects the real token automatically. - Dockerfile Dependency Guard: Verifies the pinned VERCEL_VERSION arg and pnpm global install line exist in container/Dockerfile, backed by a vitest structural test that fails if either drifts. - Use Case: A user wants their NanoClaw agents to ship a Next.js app to production. Running this Skill installs the CLI, stores the token, syncs skills to live sessions, and restarts containers — after which agents can run vercel deploy --yes --prod. ## Quick Start Ask the agent to add Vercel deployment capability to your NanoClaw agents and provide your Vercel personal access token when prompted.

Frequently Asked Questions about add-vercel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give NanoClaw agents the ability to deploy to Vercel?

Run the add-vercel skill, which copies the vercel-cli container skill into container/skills, registers your Vercel token in OneCLI, syncs skills to all agent sessions, and restarts running containers. Agents can then run vercel deploy commands.

How does Vercel authentication work inside NanoClaw agent containers?

Authentication is handled by OneCLI: the HTTPS proxy injects the real Vercel token into requests to api.vercel.com. Agents pass --token placeholder on every vercel command, and OneCLI replaces it with the actual credential at the proxy level.

What Vercel token settings are required for agent deployments?

Create a personal access token at vercel.com/account/tokens with Full Account scope so agents can create projects, deploy, and manage domains. No expiration is recommended to avoid credential rotation, unless your security policy requires one.

Does the Vercel CLI need to be rebuilt into the container image?

The CLI ships in the base agent image via a pinned ARG VERCEL_VERSION and pnpm install -g step in container/Dockerfile. If those lines are missing, the skill adds them and rebuilds with container/build.sh; otherwise no rebuild is needed.

Why does vercel whoami fail with an auth error in the container?

The Vercel credential is missing or expired in OneCLI, or it was not assigned to the agent. Verify with onecli secrets list, reassign the secret to the agent, and retry vercel whoami --token placeholder.