skills/vercel/SKILL.md
Deploy and manage applications on Vercel, including preview deployments and deployment protection. Use when working with Vercel-hosted projects or configuring Vercel deployments.
npx skillsauth add openhands/extensions vercelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Vercel deployments may have Deployment Protection enabled, which requires authentication to access preview deployments. This can block automated testing and agent access to preview URLs.
If you encounter a login page or authentication requirement when accessing a Vercel preview URL, the deployment has protection enabled. Signs include:
vercel.com/login or SSO login pageTo allow agents and automated systems to access protected deployments, users need to set up Protection Bypass for Automation:
Navigate to Project Settings
Generate a Protection Bypass Secret
Using the Bypass Secret
The secret can be used in two ways:
As a Header:
curl -H "x-vercel-protection-bypass: <secret>" https://your-preview-url.vercel.app
As a Query Parameter:
https://your-preview-url.vercel.app?x-vercel-protection-bypass=<secret>
For Browser-Based Testing
?x-vercel-protection-bypass=<secret> to the preview URLIf protection bypass is not suitable, users can disable protection for preview deployments:
Do NOT repeatedly attempt to access protected URLs without the bypass secret. </IMPORTANT>
Set environment variables in Vercel Dashboard under Settings → Environment Variables, or use the Vercel CLI:
vercel env add MY_SECRET
Access in your application:
const secret = process.env.MY_SECRET;
Common Vercel CLI commands:
# Login to Vercel
vercel login
# Deploy to preview
vercel
# Deploy to production
vercel --prod
# List deployments
vercel ls
# View deployment logs
vercel logs <deployment-url>
# Pull environment variables locally
vercel env pull
tools
Create an automation that generates an async standup digest from Slack. Searches selected channels for messages since the previous workday, groups updates by project, highlights blockers and decisions, and posts a summary to a target channel.
tools
Create an automation that writes a recurring research brief. Uses Tavily MCP for web research and Notion MCP to publish the final brief with executive summary, implications, and source citations.
tools
Create an automation that triages new Linear issues. Inspects the issue title, description, team, customer, priority, and recent related issues via Linear MCP. Suggests labels, priority, likely owner, duplicates, and posts a clarifying comment.
tools
Create an automation that drafts incident retrospectives. Gathers incident-channel messages from Slack, collects linked tickets and follow-ups from Linear, and publishes a retrospective draft to Notion with a timeline, impact summary, root-cause hypotheses, and action items.