New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Add Vercel to NanoClaw

by nanocoai in nanocoai/nanoclaw

Gives NanoClaw agents the ability to deploy web apps to Vercel by installing the Vercel CLI in agent containers and wiring up credential injection through OneCLI.

MITAuto-check: warningsDevOps & Cloud

Install Add Vercel to NanoClaw

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add nanocoai/nanoclaw --skill add-vercel -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nanocoai/nanoclaw add-vercel --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-vercel .claude/skills/add-vercel && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
add-vercel
GitHub stars
31k
Token cost
~1.5k tokens
SKILL.md length
598 words
Files
4
Skills in repo
59
Repo updated
First seen
Licence
MIT

At a glance

Gives NanoClaw agents the ability to deploy web apps to Vercel by installing the Vercel CLI in agent containers and wiring up credential injection through OneCLI.

  • Works in 6 steps: Pre-flight → Install Container Skill → Configure Credentials → …
  • Letting NanoClaw agents deploy web apps to Vercel
  • SKILL.md covers Phase 1: Pre-flight, Phase 2: Install Container Skill, Phase 3: Configure Credentials and Phase 4: Ensure Vercel CLI in…, plus 4 more sections
  • Runs TypeScript scripts from its folder; calls jq, vercel and rsync

What it does

The setup runs in phases. A pre-flight step checks whether the Vercel container skill is already installed and whether OneCLI works, and tells you to run /init-onecli first if it does not. The next phase copies the bundled container skill into the container skills directory and checks it.

The credential phase looks in OneCLI for an existing Vercel secret, then asks you to create a Vercel personal access token and paste it, which the agent stores as a generic OneCLI secret. Because OneCLI uses selective secret mode, the secret must be assigned to each agent explicitly. The folder also holds a REMOVE.md for undoing the change, and the excerpt stops before the later phases.

When your agent uses it

  • Letting NanoClaw agents deploy web apps to Vercel
  • Adding Vercel CLI access to agent containers
  • Configuring credential injection for api.vercel.com

Example prompts

  • “Add Vercel deployment to my NanoClaw agents.”
  • “Set up Vercel for our NanoClaw containers and walk me through the token step.”
  • “Check whether the Vercel container skill is already installed.”

Requirements

  • A NanoClaw installation with agent containers
  • OneCLI installed and working
  • A Vercel personal access token

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Pre-flight
  2. Install Container Skill
  3. Configure Credentials
  4. Ensure Vercel CLI in Container Image
  5. Sync Skills to Running Agent Groups
  6. Restart Running Containers

What it can do on your machine

Read from SKILL.md and the folder at commit 66f0823. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • jq
    • vercel
    • rsync
    • pnpm
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • vercel.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Add Vercel to NanoClaw loads about 1.5k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 598 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • WarningContains instruction-override wording (e.g. “without asking the user”)SKILL.md:10
    **Principle:** Do the work — don't tell the user to do it. Only ask for their input when it genuinely requires manual ac

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nanocoai/nanoclaw at commit 66f0823, republished under its MIT licence (© nanocoai). 598 words, ~1,481 tokens.

Download SKILL.mdSave it as .claude/skills/add-vercel/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
add-vercel
description
Add Vercel deployment capability to NanoClaw agents. Installs the Vercel CLI in agent containers and sets up OneCLI credential injection for api.vercel.com. Use when the user wants agents to deploy web applications to Vercel.

Add Vercel

This skill gives NanoClaw agents the ability to deploy web applications to Vercel. It installs the Vercel CLI in agent containers and configures OneCLI to inject Vercel credentials automatically.

Principle: Do the work — don't tell the user to do it. Only ask for their input when it genuinely requires manual action (pasting a token).

Phase 1: Pre-flight

Check if already applied

Check if the container skill exists:

bash
test -d container/skills/vercel-cli && echo "INSTALLED" || echo "NOT_INSTALLED"

If INSTALLED, skip to Phase 3 (Configure Credentials).

Check prerequisites

Verify OneCLI is working (required for credential injection):

bash
onecli version 2>/dev/null && echo "ONECLI_OK" || echo "ONECLI_MISSING"

If ONECLI_MISSING, tell the user to run /init-onecli first, then retry /add-vercel. Stop here.

Phase 2: Install Container Skill

Copy the bundled container skill into the container skills directory:

bash
rsync -a .claude/skills/add-vercel/container-skills/ container/skills/

Verify:

bash
head -5 container/skills/vercel-cli/SKILL.md

Phase 3: Configure Credentials

Check if Vercel credential already exists
bash
onecli secrets list 2>/dev/null | grep -i vercel

If a Vercel credential already exists, skip to Phase 4.

Set up Vercel API credential

The agent needs a Vercel personal access token. Tell the user:

I need your Vercel personal access token. Go to https://vercel.com/account/tokens and create one with these settings:

  • Token name: nanoclaw (or any name you'll recognize)
  • Scope: "Full Account" — the agent needs to create projects, deploy, and manage domains
  • Expiration: "No expiration" recommended (avoids credential rotation), or pick a date if your security policy requires it

After creating the token, copy it — you'll only see it once.

Once the user provides the token, add it to OneCLI:

bash
onecli secrets create \
  --name "Vercel API Token" \
  --type generic \
  --value "<TOKEN>" \
  --host-pattern "api.vercel.com" \
  --header-name "Authorization" \
  --value-format "Bearer {value}"

Verify:

bash
onecli secrets list | grep -i vercel
Assign the secret to all agents

OneCLI uses selective secret mode — secrets must be explicitly assigned to each agent. Get the Vercel secret ID from the output above, then assign it to every agent:

bash
# set-secrets replaces the entire list — read and merge for each agent.
VERCEL_SECRET_ID=$(onecli secrets list | jq -r '.data[] | select(.name | test("(?i)vercel")) | .id' | head -1)
for agent in $(onecli agents list | jq -r '.data[].id'); do
  CURRENT=$(onecli agents secrets --id "$agent" | jq -r '[.data[]] | join(",")')
  MERGED=$(printf '%s' "$CURRENT,$VERCEL_SECRET_ID" | tr ',' '\n' | sort -u | paste -sd ',' -)
  onecli agents set-secrets --id "$agent" --secret-ids "$MERGED"
done

Phase 4: Ensure Vercel CLI in Container Image

The Vercel CLI is not in the agent image by default — this skill is what adds it. It goes in container/cli-tools.json as a json-merge rather than a Dockerfile edit, which is what keeps the change deterministic and removable.

bash
grep -q '"vercel"' container/cli-tools.json && echo "PRESENT" || echo "MISSING"

If MISSING, append the entry, keeping an exact pinned version — the manifest rejects ranges, so the supply-chain policy still applies:

json
{ "name": "vercel", "version": "52.2.1" }

Then apply it:

bash
./container/build.sh

On an install that builds its own image, that rebuilds it. On one that fetches a published image, the same command adds Vercel as a single layer on top of the image already there, so the publisher's patched components underneath are kept — you are adding a tool, not replacing the runtime. The command says what that does and does not cover.

If PRESENT, the CLI is already in the manifest — skip the rebuild.

Show full SKILL.md (193 more words)Show less

Phase 4b: Copy and Run the Dependency Guard

The Vercel CLI is a globally-installed binary — not importable or typed — so a structural test guards the install. Copy it into the host test tree and run it:

bash
cp .claude/skills/add-vercel/vercel-manifest.test.ts src/vercel-manifest.test.ts
pnpm exec vitest run src/vercel-manifest.test.ts

The test asserts both halves of the install: a pinned vercel entry in container/cli-tools.json, and the container skill at container/skills/vercel-cli/. Either alone is a broken install — a manifest entry with no skill leaves the agent a binary nobody told it about, and a skill with no entry tells it to run a command that is not there.

Phase 5: Sync Skills to Running Agent Groups

Container skills are copied once at group creation and not auto-synced. After installing or updating a container skill, sync it to all existing agent groups:

bash
for session_dir in data/v2-sessions/ag-*; do
  if [ -d "$session_dir/.claude-shared/skills" ]; then
    rsync -a container/skills/ "$session_dir/.claude-shared/skills/"
    echo "Synced skills to: $session_dir"
  fi
done

Phase 6: Restart Running Containers

Stop all running agent containers so they pick up the new skills on next wake:

bash
docker ps --filter label=nanoclaw-session -q | xargs -r docker stop

Done

The agent can now deploy web applications to Vercel. Key commands:

  • vercel deploy --yes --prod --token placeholder — deploy to production
  • vercel ls --token placeholder — list deployments
  • vercel whoami --token placeholder — check auth

For the full command reference, the agent has the vercel-cli container skill loaded automatically.

© nanocoai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in .claude/skills/add-vercel of nanocoai/nanoclaw.

  • SKILL.md
  • REMOVE.md
  • container-skills
  • vercel-manifest.test.ts

Open the folder on GitHubat commit 66f0823

Compare with similar skills

Add Vercel to NanoClaw next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Add Vercel to NanoClaw compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Vercel to NanoClaw this skillnanocoai/nanoclaw31k—~1.5kAutomated safety check: WarnMIT
Clay Deploy Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: PassMIT
Vercel CLI With Tokensvercel-labs/agent-skills32k7 repos~2.6kAutomated safety check: NotesNone
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Monstermq Broker Configvogler75/monster-mq143—~2.2kAutomated safety check: PassGPL-3.0
Deploymentmatrixorigin/memoria609—~1.6kAutomated safety check: NotesApache-2.0

Similar skills

  • Clay Deploy Integration

    jeremylongshore/tons-of-skills-marketplace

    Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management.

    2.8k GitHub stars~1.8k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Vercel CLI With Tokens

    vercel-labs/agent-skills

    Official

    Deploys and manages Vercel projects through the CLI using an access token from the environment or a .env file instead of interactive login.

    32k GitHub starsUsed in 7 repos~2.6k tokens
    DevOps & CloudAuto-check: notes

  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Monstermq Broker Config

    vogler75/monster-mq

    Guide for configuring, deploying, and operating the MonsterMQ broker.

    143 GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Deployment

    matrixorigin/memoria

    Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.

    609 GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Env Manager

    bobmatnyc/claude-mpm

    Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms

    155 GitHub stars~2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

More from nanocoai/nanoclaw

All 59 skills in this repo

  • Iron Proxy Gateway for NanoClaw

    nanocoai/nanoclaw

    Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.

    31k GitHub stars~4.6k tokensUpdated 2 days ago
    Auto-check: notes

  • NanoClaw OneCLI Gateway Installer

    nanocoai/nanoclaw

    Installs or refreshes OneCLI as the gateway provider for NanoClaw, copying the adapter files, registering the provider and running the setup script.

    31k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check: notes

  • Agent Browser

    nanocoai/nanoclaw

    Drives a web browser from the shell with the agent-browser CLI: open pages, read an element snapshot, click and fill by reference, grab text and screenshots.

    31k GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed

  • OpenClaw to NanoClaw Migration

    nanocoai/nanoclaw

    Guides a conversational migration from an OpenClaw install to NanoClaw v2, carrying over identity, channel credentials, scheduled tasks and workspace files.

    31k GitHub stars~6k tokensUpdated 2 days ago
    Auto-check: notes

  • Add A Second Dial Phone Number

    nanocoai/nanoclaw

    Wires up an additional phone number onto an already-installed Dial channel, so one NanoClaw install answers SMS and AI voice calls on more than one line.

    31k GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed

  • Add Dial Tool

    nanocoai/nanoclaw

    Installs the `dial` CLI and a credential in NanoClaw agent containers so chosen agents can send SMS, place AI voice calls and receive verification codes.

    31k GitHub stars~4.4k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Add Vercel to NanoClaw

What does Add Vercel to NanoClaw do?

Gives NanoClaw agents the ability to deploy web apps to Vercel by installing the Vercel CLI in agent containers and wiring up credential injection through OneCLI. The setup runs in phases. A pre-flight step checks whether the Vercel container skill is already installed and whether OneCLI works, and tells you to run /init-onecli first if it does not.

When should I use Add Vercel to NanoClaw?

Add Vercel to NanoClaw fits situations like: letting NanoClaw agents deploy web apps to Vercel; adding Vercel CLI access to agent containers; configuring credential injection for api.vercel.com.

How do I install Add Vercel to NanoClaw in Claude Code?

Run `npx skills add nanocoai/nanoclaw --skill add-vercel -a claude-code`. Or copy the skill folder (.claude/skills/add-vercel in nanocoai/nanoclaw) into .claude/skills/add-vercel in your project. Claude Code loads it when a task matches its description.

How do I install Add Vercel to NanoClaw in Codex?

Run `npx skills add nanocoai/nanoclaw --skill add-vercel -a codex`. Or copy the skill folder (.claude/skills/add-vercel in nanocoai/nanoclaw) into .agents/skills/add-vercel in your project. Codex loads it when a task matches its description.

Can I use Add Vercel to NanoClaw in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nanocoai/nanoclaw --skill add-vercel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-vercel, .gemini/skills/add-vercel, .github/skills/add-vercel and .opencode/skills/add-vercel in your project.

What does Add Vercel to NanoClaw need to run?

Going by SKILL.md and its folder, Add Vercel to NanoClaw needs TypeScript for the scripts in its folder and the command-line tools its instructions call (jq, vercel, rsync, pnpm and docker). Our summary lists: A NanoClaw installation with agent containers; OneCLI installed and working; A Vercel personal access token.

Does Add Vercel to NanoClaw access the network?

SKILL.md names 1 domain. As links in the text: vercel.com. This is read from the text; nothing was executed.

Is Add Vercel to NanoClaw safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): contains instruction-override wording (e.g. “without asking the user”). Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Add Vercel to NanoClaw use?

Add Vercel to NanoClaw is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Vercel to NanoClaw use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Vercel to NanoClaw?

Skills that share tags, products or a category with Add Vercel to NanoClaw: Clay Deploy Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Vercel CLI With Tokens (vercel-labs/agent-skills, 32k stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars) and Monstermq Broker Config (vogler75/monster-mq, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Vercel to NanoClaw?

nanocoai (a GitHub organization) maintains it in nanocoai/nanoclaw, which has 30,902 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on October 6, 2026.

Source: nanocoai/nanoclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.