vercel
Deploy applications and manage projects with complete CLI reference. Commands for deployments, projects, domains, environment variables, and live documentation access.
What this skill does
# Vercel Complete Vercel CLI reference and documentation access. ## When to Use - Deploying applications to Vercel - Managing projects, domains, and environment variables - Running local development server - Viewing deployment logs and status - Looking up Vercel documentation --- ## Documentation Fetch any Vercel docs page as markdown: ```bash curl -s "https://vercel.com/docs/<path>" -H 'accept: text/markdown' ``` **Get the full sitemap to discover all available pages:** ```bash curl -s "https://vercel.com/docs/sitemap.md" -H 'accept: text/markdown' ``` --- ## CLI Commands ### Deployment #### `vercel` / `vercel deploy [path]` Deploy the current directory or specified path. **Options:** - `--prod` - Deploy to production - `-e KEY=VALUE` - Set runtime environment variables - `-b KEY=VALUE` - Set build-time environment variables - `--prebuilt` - Deploy prebuilt output (use with `vercel build`) - `--force` - Force new deployment even if unchanged - `--no-wait` - Don't wait for deployment to finish - `-y, --yes` - Skip prompts, use defaults **Examples:** ```bash vercel # deploy current directory vercel --prod # deploy to production vercel /path/to/project # deploy specific path vercel -e NODE_ENV=production # with env var vercel build && vercel --prebuilt # prebuilt deploy ``` #### `vercel build` Build the project locally into `./vercel/output`. ```bash vercel build ``` #### `vercel dev [dir]` Start local development server. **Options:** - `-l, --listen <URI>` - Port/address (default: 0.0.0.0:3000) **Examples:** ```bash vercel dev # start on port 3000 vercel dev --listen 8080 # start on port 8080 ``` --- ### Project Management #### `vercel link [path]` Link local directory to a Vercel project. **Options:** - `-p, --project <NAME>` - Specify project name - `-y, --yes` - Skip prompts **Examples:** ```bash vercel link vercel link --yes vercel link -p my-project ``` #### `vercel projects` Manage projects. ```bash vercel projects list # list all projects vercel projects add <name> # create new project vercel projects inspect [name] # show project details vercel projects remove <name> # delete project ``` #### `vercel pull [path]` Pull project settings and env vars from cloud. ```bash vercel pull ``` --- ### Environment Variables #### `vercel env` Manage environment variables. ```bash vercel env list [environment] # list env vars vercel env add <name> [environment] # add env var vercel env remove <name> [environment] # remove env var vercel env pull [filename] # pull to .env.local ``` **Environments:** `development`, `preview`, `production` **Examples:** ```bash vercel env list production vercel env add DATABASE_URL production vercel env pull .env.local ``` --- ### Domains & Aliases #### `vercel domains` Manage domain names. ```bash vercel domains list # list domains vercel domains add <domain> <project> # add domain vercel domains inspect <domain> # show domain info vercel domains remove <domain> # remove domain vercel domains buy <domain> # purchase domain vercel domains transfer-in <domain> # transfer domain to Vercel ``` #### `vercel alias` Manage deployment aliases. ```bash vercel alias list # list aliases vercel alias set <deployment> <alias> # create alias vercel alias remove <alias> # remove alias ``` **Examples:** ```bash vercel alias set my-app-abc123.vercel.app my-app.vercel.app vercel alias set my-app-abc123.vercel.app custom-domain.com ``` --- ### Deployments #### `vercel ls [app]` / `vercel list` List deployments. ```bash vercel ls vercel ls my-project ``` #### `vercel inspect [id]` Display deployment information. ```bash vercel inspect <deployment-url-or-id> ``` #### `vercel logs <url|id>` View runtime logs for a deployment. **Options:** - `-j, --json` - Output as JSON (compatible with jq) **Examples:** ```bash vercel logs my-app.vercel.app vercel logs <deployment-id> --json vercel logs <deployment-id> --json | jq 'select(.level == "error")' ``` #### `vercel promote <url|id>` Promote deployment to production. ```bash vercel promote <deployment-url-or-id> ``` #### `vercel rollback [url|id]` Rollback to previous deployment. ```bash vercel rollback vercel rollback <deployment-url-or-id> ``` #### `vercel redeploy [url|id]` Rebuild and deploy a previous deployment. ```bash vercel redeploy <deployment-url-or-id> ``` #### `vercel rm <id>` / `vercel remove` Remove a deployment. ```bash vercel rm <deployment-url-or-id> ``` --- ### Authentication & Teams ```bash vercel login [email] # log in or create account vercel logout # log out vercel whoami # show current user vercel switch [scope] # switch between scopes/teams vercel teams # manage teams ``` --- ### Other Commands ```bash vercel open # open project in dashboard vercel init [example] # initialize from example vercel install [name] # install marketplace integration vercel integration # manage integrations vercel certs # manage SSL certificates vercel dns # manage DNS records vercel bisect # binary search for bug-introducing deployment ``` --- ## Global Options Available on all commands: | Option | Description | |--------|-------------| | `-h, --help` | Show help | | `-v, --version` | Show version | | `-d, --debug` | Debug mode | | `-t, --token <TOKEN>` | Auth token | | `-S, --scope` | Set scope/team | | `--cwd <DIR>` | Working directory | | `-A, --local-config <FILE>` | Path to vercel.json | | `--no-color` | Disable colors | --- ## Quick Reference | Task | Command | |------|---------| | Deploy | `vercel` or `vercel --prod` | | Dev server | `vercel dev` | | Link project | `vercel link` | | List deployments | `vercel ls` | | View logs | `vercel logs <url>` | | Add env var | `vercel env add <name> <env>` | | Pull env vars | `vercel env pull` | | Rollback | `vercel rollback` | | Add domain | `vercel domains add <domain> <project>` | | Get docs | `curl -s "https://vercel.com/docs/<path>" -H 'accept: text/markdown'` | | Docs sitemap | `curl -s "https://vercel.com/docs/sitemap.md" -H 'accept: text/markdown'` |
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.