investigation-mode

Triage runtime logs, workflow statuses, and deployment configurations to identify root causes.

246|42|Updated Mar 4, 2026

Search Tags:#debugging #troubleshooting #logs #error handling #vercel #triage

Ready to run

npx skills add https://github.com/vercel-labs/vercel-plugin --skill investigation-mode-vercel-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigation-mode
Source: https://github.com/vercel-labs/vercel-plugin/tree/main/skills/investigation-mode
Command: npx skills add https://github.com/vercel-labs/vercel-plugin --skill investigation-mode-vercel-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as an orchestrated debugging coordinator, systematically triaging issues when applications become stuck, hung, or unresponsive, preventing user frustration and downtime.

Core Features & Use Cases

Systematic Triage: Follows a strict order: runtime logs, workflow status, browser verification, and deployment/environment checks.
Clear Reporting: Reports findings at every step, ensuring the user is informed throughout the debugging process.
Root Cause Identification: Stops as soon as a high-confidence root cause is identified, avoiding unnecessary steps.
Use Case: When a user reports their Next.js app is showing a blank page after deployment, this Skill will first check Vercel logs, then workflow runs, then attempt a browser verification, and finally inspect the deployment status to pinpoint the error.

Quick Start

Use the investigation-mode skill to debug why the application is stuck.

Frequently Asked Questions about investigation-mode

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

FAQPage Schema

How do I debug a stuck or hung Next.js app on Vercel?▼

Debugging an unresponsive application requires triaging runtime logs, workflow statuses, browser verification, and deployment configurations sequentially to identify the root cause of the hang or timeout.

What is the best way to troubleshoot Vercel deployment errors?▼

Troubleshooting Vercel deployment errors involves a strict triage order: inspecting runtime logs first, then workflow runs, followed by browser verification, and finally checking deployment status to find high-confidence root causes.

Why does my application show a blank page after a Vercel deployment?▼

A blank page after deployment often indicates an application hang or timeout. Systematic debugging checks Vercel logs, workflow runs, and browser verification to identify the specific runtime error or deployment misconfiguration.

Can I use a systematic triage workflow for application timeouts?▼

Yes, a systematic triage workflow is ideal for application timeouts. It orchestrates diagnostics across logs, workflows, and deployments, stopping immediately once a high-confidence root cause is identified to avoid unnecessary steps.

When should I stop investigating application errors during triage?▼

You should stop investigating application errors during triage as soon as a high-confidence root cause is identified. This prevents unnecessary diagnostic steps and ensures clear reporting at each completed verification stage.