agentleFS
Sign inStart free
OpenHandsOpenHands/extensions/skills/vercel/SKILL.md

vercel

Skill167 starsChanged 27 days agoMITView on GitHub

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

  • Reads credentials

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use analytics-metrics, aws-account-management and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • hoodiniSkill

    analytics-metrics

    Build data visualization and analytics dashboards. Use when creating charts, KPI displays, metrics dashboards, or data visualization components. Triggers on analytics, dashboard, charts, metrics, KPI, data visualization, Recharts.

    Also in 3 projects that use this

  • hoodiniSkill

    aws-account-management

    Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, Identity Center.

    Also in 3 projects that use this

  • imehrSkill

    railway

    Railway.com deployment and management - deployment, logs, migrations, troubleshooting, monorepo strategies, security, and CLI reference. Use when deploying to Railway, configuring services, managing environment variables, or debugging deployment issues.

    Also in 6 projects that use this

  • VercelSkill

    twilio

    Emulated Twilio REST APIs for local development and testing. Use when the user needs to test Twilio Messaging, Verify, Voice, phone numbers, webhooks, status callbacks, inbound SMS simulation, or Twilio SDK integrations without hitting the real Twilio service.

    Also in 3 projects that use this

  • LangChainSkill

    langchain

    Build agents with a prebuilt architecture and integrations for any model or tool. Use when creating tool-calling agents, switching model providers, or adding structured output.

    Also in 3 projects that use this

  • +7 more from hoodini

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you encounter a login page or authentication requirement when accessing a Vercel preview URL, the deployment has protection enabled.

    line 17
  2. Distinctive:

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

    line 60
  3. Distinctive:

    If you cannot access a Vercel preview deployment due to authentication requirements, inform the user that they need to either:

    line 66
  4. Distinctive:

    Do NOT repeatedly attempt to access protected URLs without the bypass secret.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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:

    curl -H "x-vercel-protection-bypass: <secret>" https://your-preview-url.vercel.app

    PowerShell equivalent:

    Invoke-WebRequest -Headers @{ "x-vercel-protection-bypass" = "<secret>" } -Uri 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
<IMPORTANT> If you cannot access a Vercel preview deployment due to authentication requirements, inform the user that they need to either: 1. Set up a Protection Bypass secret and provide it to you, OR 2. Disable Deployment Protection for preview deployments in their Vercel project settings

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free