openhands/vercel
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.
$ install --global
skillsauthnpx skillsauth add openhands/skills vercelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 2, 2026, 6:31 AM222.1s2 files scanned
SKILL.md
- name:
- vercel
- description:
- Deploy and manage applications on Vercel, including preview deployments and deployment protection. Use when working with Vercel-hosted projects or configuring Vercel deployments.
Vercel Deployment Guide
Deployment Protection and Agent Access
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.
Identifying Protected Deployments
If you encounter a login page or authentication requirement when accessing a Vercel preview URL, the deployment has protection enabled. Signs include:
- Redirect to
vercel.com/loginor SSO login page - 401/403 errors when accessing the deployment
- Preview URLs that require Vercel team membership
Enabling Agent Access with Protection Bypass
To allow agents and automated systems to access protected deployments, users need to set up Protection Bypass for Automation:
-
Navigate to Project Settings
- Go to the Vercel Dashboard
- Select the project
- Click on Settings → Deployment Protection
-
Generate a Protection Bypass Secret
- Under "Protection Bypass for Automation", click Generate Secret
- Copy the generated secret securely
-
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.appPowerShell equivalent:
Invoke-WebRequest -Headers @{ "x-vercel-protection-bypass" = "<secret>" } -Uri https://your-preview-url.vercel.appAs a Query Parameter:
https://your-preview-url.vercel.app?x-vercel-protection-bypass=<secret> -
For Browser-Based Testing
- Append
?x-vercel-protection-bypass=<secret>to the preview URL - The secret will be stored in a cookie for subsequent requests
- Append
Alternative: Disable Protection for Previews
If protection bypass is not suitable, users can disable protection for preview deployments:
- Go to Settings → Deployment Protection
- Set "Vercel Authentication" to Only Production Deployments or Disabled
Do NOT repeatedly attempt to access protected URLs without the bypass secret. </IMPORTANT>
Environment Variables
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;
Vercel CLI Commands
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
Related Skills
openhands/iterate
tools
VerifiedTrustedCommunity
Iterate on a GitHub pull request — drive it through CI, code review, and QA until it is merge-ready. Poll verification layers with `gh` CLI, diagnose and fix CI failures, address review feedback, retry flaky checks, push fixes, and repeat. The agent is the orchestration loop.
125SKILL.mdUpdated Apr 18, 2026
openhands/technical-writing
development
VerifiedTrustedCommunity
Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering chat, design discussion, architecture analysis, code-review explanations, and technical recommendations that should be concise without becoming fragmented or vague.
124SKILL.mdUpdated Jul 13, 2026
openhands/jira-issue-to-pr
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a Jira issue-to-PR automation", "create a Jira to GitHub PR workflow", or mentions automating GitHub PR creation from a Jira label. Deploys a cron-based OpenHands automation that watches a Jira Cloud project for issues labeled with a configurable label (default: "create-pr") and spawns an agent conversation to create a GitHub pull request for each new issue found. The target GitHub repository is read from the body of the Jira ticket - no repo parameter is required at deploy time.
123SKILL.mdUpdated Jul 7, 2026
openhands/openhands-automation
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "create an automation", "schedule a task", "set up a cron job", "webhook integration", "event-triggered automation", or mentions automations, scheduled tasks, cron scheduling, or webhook events in OpenHands Cloud.
123SKILL.mdUpdated Apr 24, 2026