New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vercel Common Errors

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Diagnose and fix common Vercel deployment and function errors.

MITAuto-check passedBackend & APIs

Install Vercel Common Errors

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-common-errors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace vercel-common-errors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/vercel-common-errors .claude/skills/vercel-common-errors && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vercel-common-errors
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
665 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Diagnose and fix common Vercel deployment and function errors.

  • Works in 5 steps: Identify the Error Layer → Build Errors → Runtime Errors → …
  • Encountering Vercel errors
  • SKILL.md covers Overview, Prerequisites, Instructions and Quick Diagnosis Flowchart, plus 5 more sections
  • Calls vercel and npm; reaches api.vercel.com; needs VERCEL_TOKEN

What it does

Vercel Common Errors is an agent skill from jeremylongshore/tons-of-skills-marketplace. Diagnose and fix common Vercel deployment and function errors. Use when encountering Vercel errors, debugging failed deployments, or troubleshooting serverless function issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel", "vercel 500", "vercel build failed".

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/errors.md` and `references/examples.md`). Compatibility notes: Designed for Claude Code

It sits in Backend & APIs, covering Deployment, Serverless and Debugging. It works with Vercel and npm. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Encountering Vercel errors
  • Debugging failed deployments
  • Troubleshooting serverless function issues
  • With phrases like vercel error

Example prompts

  • “vercel error”
  • “fix vercel”
  • “vercel not working”
  • “/vercel-common-errors”

Requirements

  • Node.js
  • A credential in VERCEL_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Grep, Bash(vercel:*), Bash(curl:*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify the Error Layer
  2. Build Errors
  3. Runtime Errors
  4. Edge/Routing Errors
  5. Environment Variable Errors

What it can do on your machine

Read from SKILL.md and the folder at commit 23ea8d4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Bash(vercel:*)
    • Bash(curl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • vercel
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.vercel.com

    Also links to:

    • vercel.com
    • vercel-status.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • VERCEL_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Vercel Common Errors loads about 1.8k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 665 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 23ea8d4, republished under its MIT licence (© jeremylongshore). 665 words, ~1,808 tokens.

Download SKILL.mdSave it as .claude/skills/vercel-common-errors/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
vercel-common-errors
description
Diagnose and fix common Vercel deployment and function errors. Use when encountering Vercel errors, debugging failed deployments, or troubleshooting serverless function issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel", "vercel 500", "vercel build failed".
allowed-tools
Read, Grep, Bash(vercel:*), Bash(curl:*)
compatibility
Designed for Claude Code
version
1.18.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, vercel, debugging, errors

Vercel Common Errors

Overview

Diagnose and resolve the most common Vercel errors across three layers: build pipeline, serverless function runtime, and edge network. Each error includes the error code, root cause, and step-by-step fix.

Prerequisites

  • Vercel CLI installed
  • Access to deployment logs (vercel logs <url>)
  • Access to Vercel dashboard for build logs

Instructions

Step 1: Identify the Error Layer
text
# Check deployment status and error details
vercel inspect <deployment-url>

# View function runtime logs
vercel logs <deployment-url> --follow

# View build logs via API
curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \
  "https://api.vercel.com/v13/deployments/dpl_xxx" | jq '.state, .errorMessage'

Three error layers:

  1. Build errors — appear during vercel deploy, exit codes in build log
  2. Runtime errors — appear when functions are invoked, visible in function logs
  3. Edge/routing errors — HTTP errors from Vercel's edge network
Step 2: Build Errors

BUILD_FAILED — Build command exited with non-zero code

Error: Command "npm run build" exited with 1
  • Check: vercel.json → buildCommand matches your build script
  • Check: all dependencies listed in package.json (not just devDependencies for runtime deps)
  • Fix: run npm run build locally to reproduce

MISSING_BUILD_SCRIPT — No build command found

Error: Missing Build Command
  • Fix: add "build" to package.json scripts or set buildCommand in vercel.json
  • For static sites: set buildCommand to empty string or "true"

FUNCTION_PAYLOAD_TOO_LARGE — Serverless function bundle > 250 MB

Error: The Serverless Function "api/heavy" is 267 MB which exceeds the maximum size of 250 MB
  • Fix: add unused packages to .vercelignore, use dynamic imports, split into smaller functions
  • Check: @vercel/nft trace output to see what is being bundled
Step 3: Runtime Errors

FUNCTION_INVOCATION_FAILED — Unhandled exception in function

bash
# View the actual error
vercel logs <deployment-url> --output=short
  • Common causes: undefined env var, missing database connection, unhandled promise rejection
  • Fix: wrap handler in try/catch, verify all env vars are set for the target environment

FUNCTION_INVOCATION_TIMEOUT — Function exceeded max duration

Error: Task timed out after 10.00 seconds
  • Hobby: 10s max, Pro: 60s default (up to 300s), Enterprise: 900s
  • Fix: optimize database queries, add connection pooling, or move to background processing
  • Configure in vercel.json:
json
{
  "functions": {
    "api/slow-endpoint.ts": {
      "maxDuration": 60
    }
  }
}

NO_RESPONSE_FROM_FUNCTION — Function didn't return a response

  • Cause: handler has a code path that doesn't call res.send(), res.json(), or return a Response
  • Fix: ensure ALL code paths return a response, including error handlers

FUNCTION_THROTTLED — Too many concurrent function invocations

  • Hobby: 10 concurrent, Pro: 1000 concurrent
  • Fix: implement client-side retry with backoff, or upgrade plan
Step 4: Edge/Routing Errors

404 NOT_FOUND

  • API route 404: verify file is in api/ or pages/api/ directory
  • Page 404: check outputDirectory in vercel.json, verify build output contains the file
  • Fix: run vercel inspect <url> to see the deployment file listing

504 GATEWAY_TIMEOUT

  • Serverless function exceeded its timeout — same as FUNCTION_INVOCATION_TIMEOUT
  • Fix: increase maxDuration or optimize function

413 REQUEST_ENTITY_TOO_LARGE

  • Request body exceeds 4.5 MB limit
  • Fix: use chunked upload, stream the body, or use presigned URLs for large files

DEPLOYMENT_NOT_FOUND

  • Deployment was deleted or URL is malformed
  • Fix: verify the deployment still exists with vercel ls
Show full SKILL.md (263 more words)Show less
Step 5: Environment Variable Errors

ReferenceError: process is not defined (Edge Runtime)

  • Cause: using process.env in an edge function
  • Fix: Edge Functions can read env vars but only those defined at build time. Ensure vars are set.

Env var undefined in production but works in preview

  • Cause: variable scoped to Preview only, not Production
  • Fix: check scopes in Settings > Environment Variables, add Production target
bash
# Check which environments have the variable
vercel env ls | grep DATABASE_URL

Quick Diagnosis Flowchart

Error occurred
├── During build? → Check build logs, run `npm run build` locally
├── During function invocation? → Check function logs with `vercel logs`
├── HTTP 404? → Verify file exists in deployment: `vercel inspect`
├── HTTP 500? → Unhandled exception in function code
├── HTTP 504? → Function timeout — increase maxDuration
└── HTTP 429? → Rate limited — implement retry with backoff

Output

  • Error layer identified (build, runtime, or edge)
  • Root cause diagnosed using logs and inspection
  • Fix applied and verified via new deployment
  • Prevention measures documented

Error Handling

Error CodeHTTPLayerQuick Fix
BUILD_FAILED—BuildRun build locally, check deps
FUNCTION_INVOCATION_FAILED500RuntimeCheck env vars, add try/catch
FUNCTION_INVOCATION_TIMEOUT504RuntimeIncrease maxDuration in vercel.json
FUNCTION_THROTTLED429RuntimeReduce concurrency or upgrade plan
FUNCTION_PAYLOAD_TOO_LARGE413BuildReduce bundle size
NOT_FOUND404EdgeVerify file paths and routes
EDGE_FUNCTION_INVOCATION_FAILED500EdgeRemove Node.js APIs from edge code
NO_RESPONSE_FROM_FUNCTION502RuntimeReturn response from all code paths

Examples

Repair a production-only missing environment variable

When a route works in preview but returns a production 500, first confirm the variable’s target scope with vercel env ls without printing its value. Add the secret through the project’s approved secret-management path for the Production target, redeploy a preview with a synthetic health check, and verify only that the variable is present and the route succeeds. Record the deployment URL and remove any temporary diagnostic logging before promoting the fix.

Resources

Next Steps

For detailed debug bundles, see vercel-debug-bundle.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/vercel-common-errors of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/errors.md
  • references/examples.md

Open the folder on GitHubat commit 23ea8d4

Compare with similar skills

Vercel Common Errors next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vercel Common Errors compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vercel Common Errors this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: PassMIT
Deploy Verceljohnku2011/boilerplates-with-ai-skills240—~660Automated safety check: NotesMIT
Vercel Deploymentdavila7/claude-code-templates32k5 repos~534Automated safety check: PassMIT
Frontmcp Deploymentagentfront/frontmcp146—~9.2kAutomated safety check: NotesApache-2.0
Deploy Fullstack Vercelvellum-ai/vellum-assistant1.4k—~2.8kAutomated safety check: PassMIT
Vercelhoodini/ai-agents-skills281—~1.1kAutomated safety check: NotesNone

Similar skills

  • Deploy Vercel

    johnku2011/boilerplates-with-ai-skills

    A skill your agent uses when deploying or configuring this project on Vercel — env vars, build settings, serverless limits, and production checks for Next.js or Express.

    240 GitHub stars~660 tokensUpdated 1 mo ago
    Backend & APIsAuto-check: notes

  • Vercel Deployment

    davila7/claude-code-templates

    Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.

    32k GitHub starsUsed in 5 repos~534 tokens
    DevOps & CloudAuto-check passed

  • Frontmcp Deployment

    agentfront/frontmcp

    A skill your agent uses when deploying, building for production, packaging, or shipping a FrontMCP server.

    146 GitHub stars~9.2k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

  • Deploy Fullstack Vercel

    vellum-ai/vellum-assistant

    Build and deploy a full-stack app (React frontend + Python/FastAPI backend) or a Vellum app to Vercel as a serverless demo with seeded data

    1.4k GitHub stars~2.8k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Vercel

    hoodini/ai-agents-skills

    Deploy and configure applications on Vercel. An agent skill from hoodini/ai-agents-skills.

    281 GitHub stars~1.1k tokensUpdated 2 mo ago
    Backend & APIsAuto-check: notes

  • Vercel Deploy

    aiskillstore/marketplace

    Deploy applications and websites to Vercel instantly. An agent skill from aiskillstore/marketplace.

    430 GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Analyzing Text With NLP

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to perform natural language processing and text analysis using the nlp-text-analyzer plugin.

    2.8k GitHub starsUsed in 1 repo~819 tokens
    Auto-check passed

  • Building Neural Networks

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill allows AI assistant to construct and configure neural network architectures using the neural-network-builder plugin.

    2.8k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

  • Detecting Data Anomalies

    jeremylongshore/tons-of-skills-marketplace

    Process identify anomalies and outliers in datasets using machine learning algorithms.

    2.8k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

  • Explaining Machine Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill enables AI assistant to provide interpretability and explainability for machine learning models.

    2.8k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

  • Optimizing Prompts

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill optimizes prompts for large language models (llms) to reduce token usage, lower costs, and improve performance.

    2.8k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

Works with

Categories

Questions about Vercel Common Errors

What does Vercel Common Errors do?

Diagnose and fix common Vercel deployment and function errors. Vercel Common Errors is an agent skill from jeremylongshore/tons-of-skills-marketplace. Diagnose and fix common Vercel deployment and function errors.

When should I use Vercel Common Errors?

Vercel Common Errors fits situations like: encountering Vercel errors; debugging failed deployments; troubleshooting serverless function issues; with phrases like vercel error.

How do I install Vercel Common Errors in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-common-errors -a claude-code`. Or copy the skill folder (skills/.curated/vercel-common-errors in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/vercel-common-errors in your project. Claude Code loads it when a task matches its description.

How do I install Vercel Common Errors in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-common-errors -a codex`. Or copy the skill folder (skills/.curated/vercel-common-errors in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/vercel-common-errors in your project. Codex loads it when a task matches its description.

Can I use Vercel Common Errors in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vercel-common-errors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vercel-common-errors, .gemini/skills/vercel-common-errors, .github/skills/vercel-common-errors and .opencode/skills/vercel-common-errors in your project.

What does Vercel Common Errors need to run?

Going by SKILL.md and its folder, Vercel Common Errors needs the command-line tools its instructions call (vercel and npm) and credentials named VERCEL_TOKEN. Our summary lists: Node.js; A credential in VERCEL_TOKEN. Its frontmatter pre-approves these tools: Read, Grep, Bash(vercel:*), Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Vercel Common Errors access the network?

SKILL.md names 3 domains. In commands or code: api.vercel.com; the agent is likely to contact it when it follows the instructions. As links in the text: vercel.com and vercel-status.com. This is read from the text; nothing was executed.

Is Vercel Common Errors safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vercel Common Errors use?

Vercel Common Errors is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vercel Common Errors use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 360 tokens, read only when the agent opens those files.

What are the alternatives to Vercel Common Errors?

Skills that share tags, products or a category with Vercel Common Errors: Deploy Vercel (johnku2011/boilerplates-with-ai-skills, 240 stars), Vercel Deployment (davila7/claude-code-templates, 32k stars), Frontmcp Deployment (agentfront/frontmcp, 146 stars) and Deploy Fullstack Vercel (vellum-ai/vellum-assistant, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vercel Common Errors?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,821 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 8, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.