Deploy Vercel integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Vercel-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy vercel", "vercel Vercel", "vercel production deploy", "vercel Cloud Run", "vercel Fly.io".
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install vercel-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Deploy Vercel-powered applications to popular platforms with proper secrets management.
# Add Vercel secrets to Vercel
vercel secrets add vercel_api_key sk_live_***
vercel secrets add vercel_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod
{
"env": {
"VERCEL_API_KEY": "@vercel_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}
app = "my-vercel-app"
primary_region = "iad1"
[env]
NODE_ENV = "production"
[http_service]
internal_port = 3000
force_https = true
auto_stop_machines = true
auto_start_machines = true
# Set Vercel secrets
fly secrets set VERCEL_API_KEY=sk_live_***
fly secrets set VERCEL_WEBHOOK_SECRET=whsec_***
# Deploy
fly deploy
FROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
CMD ["npm", "start"]
#!/bin/bash
# deploy-cloud-run.sh
PROJECT_ID="${GOOGLE_CLOUD_PROJECT}"
SERVICE_NAME="vercel-service"
REGION="None"
# Build and push image
gcloud builds submit --tag gcr.io/$PROJECT_ID/$SERVICE_NAME
# Deploy to Cloud Run
gcloud run deploy $SERVICE_NAME \
--image gcr.io/$PROJECT_ID/$SERVICE_NAME \
--region $REGION \
--platform managed \
--allow-unauthenticated \
--set-secrets=VERCEL_API_KEY=vercel-api-key:latest
// config/vercel.ts
interface VercelConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getVercelConfig(): VercelConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.VERCEL_API_KEY!,
environment: env as VercelConfig['environment'],
webhookSecret: process.env.VERCEL_WEBHOOK_SECRET,
};
}
// api/health.ts
export async function GET() {
const vercelStatus = await checkVercelConnection();
return Response.json({
status: vercelStatus ? 'healthy' : 'degraded',
services: {
vercel: vercelStatus,
},
timestamp: new Date().toISOString(),
});
}
Select the platform that best fits your infrastructure needs and follow the platform-specific guide below.
Store Vercel API keys securely using the platform's secrets management.
Use the platform CLI to deploy your application with Vercel integration.
Test the health check endpoint to confirm Vercel connectivity.
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via platform CLI |
| Deploy timeout | Large build | Increase build timeout |
| Health check fails | Wrong API key | Verify environment variable |
| Cold start issues | No warm-up | Configure minimum instances |
#!/bin/bash
# Platform-agnostic deploy helper
case "$1" in
vercel)
vercel secrets add vercel_api_key "$VERCEL_API_KEY"
vercel --prod
;;
fly)
fly secrets set VERCEL_API_KEY="$VERCEL_API_KEY"
fly deploy
;;
esac
For webhook handling, see vercel-webhooks-events.