Deploy and manage Vercel projects via git integration or CLI workflows.
npx skills add https://github.com/tommylower/cortex --skill vercel-deploy-tommylower
Please help me install this Agent Skill. Skill: vercel-deploy Source: https://github.com/tommylower/cortex/tree/main/agent-workflows/vercel-deploy Command: npx skills add https://github.com/tommylower/cortex --skill vercel-deploy-tommylower
.vercel linking, and authentication state to choose between git-push previews and direct vercel deploy CLI uploads. - Safety-First Defaults: Defaults to preview deployments, requires explicit user intent for production deploys, environment variable changes, or pushes, and forbids committing tokens or .env files. - Token-Based Authentication: Supports non-interactive deployment using VERCEL_TOKEN, VERCEL_ORG_ID, and VERCEL_PROJECT_ID environment variables instead of command-line flags. - Use Case: You have an unlinked prototype repo with no git remote. The Skill runs initial checks, then executes vercel deploy -y --no-wait and inspects the returned deployment URL to confirm the preview is live. ## Quick Start Deploy my current project to Vercel as a preview deployment and give me the deployment URL.High-intent search queries and answers about installing and using this skill.
Run `vercel deploy -y --no-wait` to upload the current project and receive a deployment URL without interactive prompts. Use `vercel inspect <deployment-url>` to check the deployment status afterward.
Commit your changes and push the branch to the git remote; Vercel's git integration automatically builds a preview deployment for non-production branches. Find the preview URL with `vercel ls --format json` or your git provider's checks.
Yes, export `VERCEL_TOKEN` in the environment before running the CLI rather than passing tokens as command-line flags. Optionally also export `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` to target a specific project.
Git integration triggers builds automatically when you push branches, producing preview URLs for non-production branches. CLI deployment with `vercel deploy` uploads the project directly, which suits unlinked projects, prototypes, or repos without git remotes.
Build failures after adding dev tools are commonly caused by top-level imports of dev-only packages in production code paths. Inspect your top-level imports first and move dev-only dependencies out of the runtime bundle.
Production deploys with `vercel deploy --prod` should only run when the user explicitly requests production wording. The same rule applies to pushing branches, modifying environment variables, or committing anything without explicit user intent.
masermediagroup-stackDeploy projects to Vercel and obtain preview URLs via CLI or no-auth fallback.
etylsarinManage Vercel deployments and inspect build and runtime logs.
matteingRun the full CI suite locally to verify Elixir and TypeScript checks before pushing.
dthuy62Deploy projects to hosting platforms by matching repository signals to workflows.