All skills
vercel-labs avatar

/vercel-cli

@51524a1 official

Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, managing feature flags with vercel flags, or interacting with the Vercel platform from the command line.

  • 57 files
  • 222.1 KB
  • Updated 2 weeks ago
  • GitHub

Use this Skill: https://skilld.dev/gh/vercel-labs/vercel-plugin/vercel-cli

This session only. Nothing lands on disk.

referencessandbox.md

≈626 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Sandbox

vercel sandbox forwards to the Sandbox CLI for project-scoped sandbox environments. Run vercel sandbox --help for the current list; the subcommands below are wired through sandbox/index.ts.

Subcommands

vercel sandbox list                                                              # list sandboxes (alias: ls)
vercel sandbox create                                                            # create a sandbox
vercel sandbox create --connect                                                  # create and immediately open a shell
vercel sandbox run -- node -e "console.log('hi')"                                # create + run a command in one step
vercel sandbox exec <sandbox-id> -- npm test                                     # execute a command in an existing sandbox
vercel sandbox connect <sandbox-id>                                              # interactive shell (aliases: ssh, shell)
vercel sandbox copy ./local.txt <sandbox-id>:/tmp/                               # copy files (alias: cp)
vercel sandbox stop <sandbox-id>                                                 # stop one or more sandboxes (aliases: rm, remove)
vercel sandbox config network-policy <sandbox-id> --network-policy deny-all      # update sandbox network policy
vercel sandbox snapshot <sandbox-id> --stop                                      # take a filesystem snapshot (sandbox is stopped)
vercel sandbox snapshots list                                                    # list snapshots (subcommand group: list/get/delete)
vercel sandbox login                                                             # log in to the Sandbox CLI
vercel sandbox logout                                                            # log out of the Sandbox CLI

Use -- to separate the sandbox command from arguments forwarded to the sandbox process (as in run, exec).

sandbox config is a subcommand group; the only configurable surface today is network-policy. sandbox snapshot requires --stop because snapshotting stops the sandbox first. sandbox snapshots (plural) is a separate subcommand group that manages existing snapshots (list, get, delete).

Auth Forwarding

Global Vercel flags --scope / --team / --token are forwarded to the Sandbox CLI. For automation, set VERCEL_TOKEN; the CLI maps it to VERCEL_AUTH_TOKEN for Sandbox.

Sandbox commands may create external compute or interactive sessions. Confirm intent before creating or connecting to a sandbox.

Source: SKILL.md on GitHub

No third-party reports yet.

Signed by skilld at 51524a1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 7 hours ago.

Activeupdated 2 weeks ago
Other metadata
metadata
{
  "priority": 4,
  "docs": [
    "https://vercel.com/docs/cli"
  ],
  "sitemap": "https://vercel.com/sitemap.xml",
  "pathPatterns": [
    "vercel.json",
    "vercel.ts",
    ".vercel/**",
    ".vercelignore",
    "now.json"
  ],
  "bashPatterns": [
    "^\\s*vercel(?:\\s|$)",
    "^\\s*vc(?:\\s|$)",
    "\\bnpx\\s+vercel\\b",
    "\\bpnpm\\s+dlx\\s+vercel\\b",
    "\\bbunx\\s+vercel\\b",
    "\\byarn\\s+dlx\\s+vercel\\b",
    "\\bnpx\\s+@vercel/config\\b"
  ],
  "promptSignals": {
    "phrases": [
      "check deployment",
      "check deploy",
      "deployment status",
      "deploy status",
      "vercel logs",
      "vercel metrics",
      "deployment logs",
      "deploy logs",
      "vercel inspect",
      "is it deployed",
      "deploy failing",
      "deploy failed",
      "deployment error",
      "check vercel",
      "vercel status"
    ],
    "allOf": [
      [
        "check",
        "deployment"
      ],
      [
        "check",
        "deploy"
      ],
      [
        "vercel",
        "status"
      ],
      [
        "vercel",
        "logs"
      ],
      [
        "vercel",
        "metrics"
      ],
      [
        "deploy",
        "error"
      ],
      [
        "deploy",
        "failed"
      ],
      [
        "deploy",
        "stuck"
      ]
    ],
    "anyOf": [
      "deployment",
      "deploy",
      "vercel",
      "production"
    ],
    "noneOf": [
      "terraform",
      "aws deploy",
      "heroku"
    ],
    "minScore": 6
  }
}
retrieval
{
  "aliases": [
    "vercel command line",
    "vc cli",
    "deploy command",
    "vercel terminal"
  ],
  "intents": [
    "deploy from cli",
    "link project",
    "manage domains",
    "view logs from terminal"
  ],
  "entities": [
    "vercel CLI",
    "vercel deploy",
    "vercel env",
    "vercel link",
    "vercel logs",
    "vercel metrics"
  ]
}
chainTo
[
  {
    "pattern": "\"functions\"\\s*:\\s*\\{|\"maxDuration\"\\s*:|\"memory\"\\s*:",
    "targetSkill": "vercel-functions",
    "message": "Functions configuration detected in vercel.json — loading Vercel Functions guidance for runtime options, streaming, and Fluid Compute.",
    "skipIfFileContains": "\"crons\"\\s*:"
  },
  {
    "pattern": "\"redirects\"\\s*:\\s*\\[|\"rewrites\"\\s*:\\s*\\[|\"headers\"\\s*:\\s*\\[",
    "targetSkill": "routing-middleware",
    "message": "Routing rules in vercel.json — loading Routing Middleware guidance for platform-level request interception patterns."
  }
]

README badge

README badge for vercel-labs/vercel-plugin/vercel-cli