Stats
Actions
Tags
From vercel-pack
Execute apply Vercel advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Vercel support escalation. Trigger with phrases like "vercel hard bug", "vercel mystery error", "vercel impossible to debug", "difficult vercel issue", "vercel deep debug".
How this skill is triggered — by the user, by Claude, or both
Slash command
/vercel-pack:vercel-advanced-troubleshootingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Access to production logs and metrics
Run the comprehensive debug script to gather all relevant data.
Test each layer independently to identify the failure point.
Strip down to the simplest failing case.
Use the support template with all collected evidence.
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Execute apply Vercel advanced debugging techniques for hard-to-diagnose issues.
npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin vercel-packDebugs hard-to-diagnose Vercel issues like cold starts, edge errors, intermittent failures, and function bundling using request tracing, CLI inspection, and code instrumentation.
Audits deployed Vercel apps for cost and performance issues using production metrics, config, and version-aware recommendations.
Orchestrates Vercel/Next.js work across build, deploy, audit, research, and fix lanes using parallel specialist agents and Vercel MCP deployment checks.