investigation-mode Skill
Orchestrated debugging coordinator. Triggers on frustration signals (stuck, hung, broken, waiting) and systematically triages: runtime logs → workflow status → browser verify → deploy/env. Reports findings at every step. Published by openai in plugins.
Decision snapshot
Is this a fit?
Browser automation, Deployment, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
18 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is investigation-mode Skill?
Orchestrated debugging coordinator. Triggers on frustration signals (stuck, hung, broken, waiting) and systematically triages: runtime logs → workflow status → browser verify → deploy/env. Reports findings at every step. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Deployment
- Browser automation use cases
- Deployment use cases
Declared skill metadata
- Source file: plugins/vercel/skills/investigation-mode/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use investigation-mode Skill
- Use it for browser automation.
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/vercel/skills/investigation-mode/SKILL.md
What it does
Orchestrated debugging coordinator. Triggers on frustration signals (stuck, hung, broken, waiting) and systematically triages: runtime logs → workflow status → browser verify → deploy/env. Reports findings at every step.
Skill instructions
Investigation Mode — Orchestrated Debugging When a user reports something stuck, hung, broken, or not responding, you are the diagnostic coordinator. Do not guess. Follow the triage order, report what you find at every step, and stop when you have a high-confidence root cause. Reporting Contract Every investigation step MUST follow this pattern: 1. Tell the user what you are checking — "I'm checking the runtime logs for errors…" 2. Share the evidence you found — paste the relevant log line, status, error, or screenshot 3. Explain the next step — "The logs show a timeout on the DB call. I'll check the connection pool next." Never silently move between steps. The user is already frustrated — silence makes it worse. Triage Order Work through these in order. Stop as soon as you find the root cause. 1. Runtime Logs (check first — most issues leave traces here) - Dev server: Check terminal output for errors, warnings, unhandled rejections - Vercel logs: vercel logs --follow (production) or v
Verified compatibility and discovery
Frequently asked questions
What is investigation-mode?
investigation-mode is a open-source AI agent skill with Copy skill directory. Orchestrated debugging coordinator. Triggers on frustration signals (stuck, hung, broken, waiting) and systematically triages: runtime logs → workflow status → browser verify → deploy/env.
Who is investigation-mode best for?
investigation-mode is best for reusing agent instructions, scripts, and references, browser automation workflows, deployment workflows.
How do I install investigation-mode?
Install or run investigation-mode using Copy skill directory. Check investigation-mode for the latest setup command.
Is investigation-mode actively maintained?
investigation-mode may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
