Execute diagnose and fix Vercel common errors and exceptions. Use when encountering Vercel errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel".
From vercel-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin vercel-packThis skill is limited to using the following tools:
references/errors.mdreferences/examples.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Vercel errors typically originate from one of three layers: the build pipeline (configuration errors, dependency failures), the serverless function runtime (timeouts, memory limits, environment variable issues), or the edge network (routing mismatches, header size limits). Identifying which layer is responsible saves significant debugging time before you start making changes.
Check the error message and code in your Vercel deployment logs or function logs. Build errors appear in the deployment log with exit codes and compilation output. Runtime errors appear in the function log with request context. Note the HTTP status code if the error came from a deployed function — 504 typically means a function timeout, 413 means a request payload exceeded Vercel's size limit, and 500 means an uncaught exception in your function code.
Match your error to one of the documented cases in the references file. Distinguish between errors that occur on every request (deterministic, require a code fix) and errors that occur intermittently (potentially cold-start related or caused by external service degradation). Deterministic errors should be fixed before promoting to production; intermittent errors may require retry logic or graceful degradation.
Follow the solution steps for your specific error. After applying a fix, trigger a new deployment and test the affected endpoint or route. If the error was related to environment variables, verify the variable is present in both preview and production environments in the Vercel dashboard.
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Execute diagnose and fix Vercel common errors and exceptions.