skills.rest
MarineTeam
MarineTeamCOMMUNITY
Explore all skills by this author →
GitHub

debugging-playbook

Diagnose runtime failures in a Next.js video portal from symptom to root cause.

Updated Jul 3, 2026
Search Tags:#debugging#troubleshooting#redis#vercel#nextjs#runbook#auth0
One-click install
npx skills add https://github.com/MarineTeam/fable-video --skill debugging-playbook-marineteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-playbook
Source: https://github.com/MarineTeam/fable-video/tree/main/.claude/skills/debugging-playbook
Command: npx skills add https://github.com/MarineTeam/fable-video --skill debugging-playbook-marineteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the Marine Video Portal breaks at runtime — 502 errors, login loops, missing thumbnails, failed uploads, or silent push notifications — this Skill maps the exact user-visible symptom to its root cause and fix, eliminating guesswork and blind patching. ## Core Features & Use Cases - Symptom-to-fix lookup table: Matches exact console.error log labels and HTTP statuses from pages/api/** to documented root causes and step-by-step fix runbooks. - Structured triage workflow: Enforces a reproduce → find log line → match symptom → verify sequence before any code change. - Trap warnings: Flags common false fixes, such as forgetting that Vercel env var changes require a redeploy or misreading the 4-second video-list cache as data loss. - Use Case: An admin reports every admin tab failing with 502s. The Skill identifies the Upstash Redis prefixed env var issue, points to lib/redis.js's envBySuffix() handling, and instructs verifying the variable in Vercel and redeploying. ## Quick Start Use the debugging-playbook skill to diagnose why approved viewers see "Your account is not approved to view videos" in the Marine Video Portal.

Frequently Asked Questions about debugging-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug 502 errors in a Next.js app on Vercel?▼

Find the exact console.error log line in Vercel's Logs or Functions view, since every catch block in pages/api logs before returning a 5xx. Match that label against the symptom table to get the documented root cause and fix runbook.

Why do all admin tabs fail to load with Upstash Redis errors?▼

Vercel injected a prefixed Redis env var name like fablevideo_KV_REST_API_URL instead of plain KV_REST_API_URL. The envBySuffix() helper in lib/redis.js handles this, so the fix usually just requires confirming the variable exists and redeploying.

Why does Auth0 show callback URL mismatch after upgrading?▼

Auth0 nextjs-auth0 v4 mounts routes at /auth/* instead of /api/auth/*. Update Allowed Callback URLs to https://<domain>/auth/callback in the Auth0 dashboard and confirm APP_BASE_URL exactly matches the deployed URL.

Why do bunny.net thumbnails return 403 when opened directly?▼

This is expected behavior, not a bug. The bunny.net pull zone's hotlink protection checks the Referer header, so the app's image requests work while bare URLs pasted into a browser are blocked.

When should I not use this debugging playbook?▼

Do not use it for planned code changes, dependency upgrades, security alerts, or deep incident history investigations. It covers only active runtime failures where a symptom must be traced to a root cause.

Related Skills

Explore More Software Engineering Skills→
JYHTHEGREATJYHTHEGREAT

canary

Detect post-deployment regressions by comparing Web Vitals and error logs against stored baselines.

Community
Advanced
openaiopenai
5.3k

auth

Implements Clerk, Descope, and Auth0 authentication for Next.js applications on Vercel.

Official
Intermediate
hoklimshoklims

oco-trace-stack

Analyze runtime errors and stack traces to identify root causes.

Community
Advanced
hamzaPixlhamzaPixl
2

runbook

Investigate production incidents and create runbooks using Bash and Grep.

Community
Advanced