Agent skill

vercel

Deploy and manage applications on Vercel, including preview deployments and deployment protection. Use when working with Vercel-hosted projects or configuring Vercel deployments.

View SKILL.md on GitHub Repository
Stars 78
Forks 21

Install this agent skill to your Project

npx add-skill https://github.com/OpenHands/extensions/tree/main/skills/vercel

SKILL.md

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/login or 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:

  1. Navigate to Project Settings

    • Go to the Vercel Dashboard
    • Select the project
    • Click on Settings → Deployment Protection

  2. Generate a Protection Bypass Secret

    • Under "Protection Bypass for Automation", click Generate Secret
    • Copy the generated secret securely

  3. Using the Bypass Secret

    The secret can be used in two ways:

    As a Header:

    bash
    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>

  4. 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

Alternative: Disable Protection for Previews

If protection bypass is not suitable, users can disable protection for preview deployments:

  1. Go to Settings → Deployment Protection
  2. 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:

bash
vercel env add MY_SECRET

Access in your application:

typescript
const secret = process.env.MY_SECRET;

Vercel CLI Commands

Common Vercel CLI commands:

bash
# 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

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

OpenHands/extensions

releasenotes

Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that categorize changes into breaking changes, features, fixes, and other sections.

78 21
Explore
OpenHands/extensions

bitbucket

Interact with Bitbucket repositories and pull requests using the BITBUCKET_TOKEN environment variable. Use when working with code hosted on Bitbucket or managing Bitbucket resources via API.

78 21
Explore
OpenHands/extensions

add-skill

Add an external skill from a GitHub repository to the current workspace. Use when users want to import, install, or add a skill from a GitHub URL (e.g., `/add-skill https://github.com/OpenHands/extensions/tree/main/skills/codereview` or "add the codereview skill from https://github.com/OpenHands/extensions/"). Handles fetching the skill files and placing them in .agents/skills/.

78 21
Explore
OpenHands/extensions

add-javadoc

Add comprehensive JavaDoc documentation to Java classes and methods. Use when documenting Java code, adding API documentation, or improving code documentation.

78 21
Explore
OpenHands/extensions

flarglebargle

A test skill that responds to the magic word "flarglebargle" with a compliment. Use for testing skill activation and trigger functionality.

78 21
Explore
OpenHands/extensions

codereview-roasted

Brutally honest code review in the style of Linus Torvalds, focusing on data structures, simplicity, and pragmatism. Use when you want critical, no-nonsense feedback that prioritizes engineering fundamentals over style preferences.

78 21
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results