vercel
Deploy to Vercel from command line
Deploying frontend projects to Vercel requires navigating multiple CLI commands. This skill provides ready-to-use commands for deployments, domain management, environment variables, and local development without needing to reference external documentation.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "vercel". Deploy this project to Vercel production
Resultado esperado:
- Running: vercel --prod
- Deployment initiated successfully
- View your deployment at: https://your-project.vercel.app
A utilizar "vercel". List my Vercel deployments
Resultado esperado:
- Recent deployments:
- 1. Production - https://abc.vercel.app - Ready
- 2. Preview - https://abc-dxyz.vercel.app - Ready
- 3. Preview - https://abc-qwer.vercel.app - Building
A utilizar "vercel". Pull environment variables from Vercel
Resultado esperado:
- Running: vercel env pull
- Environment variables pulled to .env file
- Found 12 variables including DATABASE_URL and API_KEY
Auditoria de Segurança
SeguroThis is a pure documentation skill containing only markdown documentation with example Vercel CLI commands. No executable code, scripts, or command execution is present. All static findings are false positives caused by the analyzer misidentifying documentation examples as code patterns. The skill is safe for publication.
Fatores de risco
⚙️ Comandos externos (50)
🌐 Acesso à rede (2)
Pontuação de qualidade
O Que Você Pode Construir
Deploy frontend applications
Quickly deploy React, Next.js, or static sites to Vercel with single commands
Manage deployment pipelines
List deployments, inspect logs, and manage environment variables across projects
Local development workflow
Run local development server and pull project settings for seamless iteration
Tente Estes Prompts
Deploy this project to Vercel using the vercel skill
Deploy this project to Vercel production using the vercel skill
List recent Vercel deployments and show their status
Pull environment variables from Vercel to local .env file
Melhores Práticas
- Run vercel whoami first to verify you are authenticated
- Use vercel env pull to sync environment variables before local development
- Test locally with vercel dev before deploying to production
Evitar
- Deploying directly to production without testing on preview deployments
- Hardcoding environment variables instead of using Vercel env management
- Skipping deployment logs review after initial deployment
Perguntas Frequentes
Is the Vercel CLI required?
What can I deploy?
How do I link a project?
Is my data safe?
Why is deployment failing?
How is this different from Vercel integrations?
Detalhes do Desenvolvedor
Autor
DicklesworthstoneLicença
MIT
Repositório
https://github.com/Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tree/main/skills/vercelReferência
main
Estrutura de arquivos
📄 SKILL.md