deploy-to-vercel
The deploy-to-vercel skill enables agents to deploy applications to the Vercel platform. It manages project linking, authentication, and deployment execution using the Vercel CLI or fallback scripts for sandboxed environments.
Is deploy-to-vercel safe to install?
Review the source first: our audit of deploy-to-vercel's source files found 21 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands, including git operations and Vercel CLI commands, and reads/writes configuration files in the .vercel directory.
How we audit skills: our security review methodology.
Who is this skill for?
Developers using AI agents to automate the deployment of web applications to Vercel.
What can you do with it?
- Deploying local projects to Vercel via git push
- Linking local directories to Vercel projects
- Performing preview deployments without git integration
- Deploying projects in sandboxed environments using fallback scripts
How good is this skill?
Quality score: 5/10. The skill provides clear, step-by-step instructions for various deployment scenarios and includes robust fallback mechanisms for sandboxed environments.
What does the skill file contain?
# Deploy to Vercel Deploy any project to Vercel. **Always deploy as preview** (not production) unless the user explicitly asks for production. The goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state. ## Step 1: Gather Project State Run all four checks before deciding which method to use: ```bash # 1. Check for a git remote git remote get-url origin 2>/dev/null # 2. Check if locally linked to a Vercel project (either file means linked) cat .vercel/project.json 2>/dev/nul...
Frequently asked questions
Does this skill deploy to production by default?
No. It defaults to preview deployments unless the user explicitly requests a production deployment.
How does the skill handle projects that are not linked to Vercel?
It attempts to link the project using the Vercel CLI, preferring repo-based linking if a git remote is detected.
What happens if the Vercel CLI is not authenticated?
The skill falls back to a deployment script that does not require authentication, providing a preview URL and a claim URL.
Related skills
find-skills
2.3MUsers seeking to extend agent capabilities with specialized tools, workflows, or knowledge packages
The find-skills skill enables agents to search for, discover, and install modular packages from the open agent skills ecosystem using the Skills CLI.
agent-browser
506.7KAI agents and developers requiring programmatic web interaction, exploratory testing, or automation of Electron desktop applications
The agent-browser CLI provides browser automation for AI agents using Chrome or Chromium via CDP. It supports page navigation, form interaction, data extraction, and testing. The tool utilizes accessibility-tree snapshots and element references for interaction.
azure-deploy
433.6KDevelopers and DevOps engineers deploying existing applications to Azure who require a structured, validated deployment process
The azure-deploy skill executes deployments for pre-configured Azure applications. It manages the deployment lifecycle using Azure Developer CLI (azd), Terraform, and Azure CLI commands, following a strict validation workflow that requires prior execution of azure-prepare and azure-validate.
microsoft-foundry
429.2KDevelopers building, deploying, and managing AI agents on Azure AI Foundry
The Microsoft Foundry skill provides a framework for the end-to-end lifecycle of AI agents, including scaffolding, deployment, evaluation, fine-tuning, and troubleshooting within Azure AI Foundry.