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.

referencesconnectors.md

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

Connectors

vercel connect manages connectors such as Slack apps. Vercel Connect is currently in beta, so behavior may change. Check vercel connect --help if a subcommand is unavailable.

Common Commands

vercel connect create slack --name my-bot
vercel connect create slack --name my-bot --triggers
vercel connect update <connector-id-or-uid> --icon ./logo.png --background-color '#1A2B3C' --accent-color '#FF0066'
vercel connect list --format=json
vercel connect list --all-projects
vercel connect list --type slack
vercel connect list --search linear --limit 10
vercel connect attach <connector-id-or-uid> -e production -e preview --yes
vercel connect detach <connector-id-or-uid> --yes
vercel connect token <connector-id-or-uid> --format=json
vercel connect open <connector-id-or-uid>
vercel connect remove <connector-id-or-uid> --disconnect-all --yes

connect token — Subject and Scopes

--subject selects whose token is returned. --installation-id targets a specific installation when the subject is app. --scopes is comma- or space-separated.

vercel connect token scl_abc123                                          # user token (default subject)
vercel connect token scl_abc123 --subject app                            # app token, default installation
vercel connect token scl_abc123 --subject app --installation-id inst_1   # app token, specific installation
vercel connect token scl_abc123 --scopes "chat:write,im:write"           # scoped token
vercel connect token scl_abc123 --yes                                    # open browser if auth/install needed
vercel connect token scl_abc123 --format=json                            # includes expiresAt, installationId

connect attach — Trigger Destinations

Pass --triggers to register the project as a webhook trigger destination. Use --trigger-branch and --trigger-path to override defaults.

vercel connect attach scl_abc123 --triggers                                                # default branch + /{service}
vercel connect attach scl_abc123 --triggers --trigger-branch staging --trigger-path /slack
vercel connect attach scl_abc123 --project my-app --triggers                               # different project

A connector accepts at most 3 trigger destinations. Use --project <name-or-id> on attach/detach when targeting a project other than the currently linked one.

Connector IDs look like scl_...; UIDs look like slack/my-bot. Either works wherever an id argument is accepted.

Connector tokens and trigger URLs can grant access to third-party systems. Do not print or store them unless the user explicitly needs that output.

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 9 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