investigate

Name: investigate
Availability: InStock
Author: Scrips

Diagnose and debug issues across the Scrips stack using a structured, evidence-based workflow.

Updated Aug 27, 2026

Search Tags:#troubleshooting #debug #dotnet #investigate #flutter #root-cause #scrips

Ready to run

npx skills add https://github.com/Scripsteam/scrips-stack --skill investigate-scripsteam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/Scripsteam/scrips-stack/tree/main/investigate
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill investigate-scripsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses production and development issues across the Scrips stack with a systematic, evidence-driven approach to reduce guesswork and MTTR.

Core Features & Use Cases

Systematic issue classification across layers (.NET API, Flutter, React Admin, database, infrastructure) to identify scope and impact.
Guided evidence gathering with concrete checks, commands, and artifacts tailored to each layer.
Hypothesis-driven debugging that documents findings, tests hypotheses, and traces root causes for reproducible fixes.
On-call troubleshooting and development debugging workflows to accelerate incident resolution and learning.

Quick Start

Start by selecting the impacted layer, classify the issue, then proceed through evidence gathering and hypothesis steps to diagnose and resolve the incident.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I debug a .NET API issue systematically across the Scrips stack?▼

You debug a .NET API issue by selecting the impacted layer, classifying the issue, and proceeding through guided evidence gathering and hypothesis steps. This structured workflow ensures reproducible fixes by documenting findings and tracing root causes.

What is the best way to troubleshoot production incidents in Flutter and React Admin?▼

Troubleshooting production incidents in Flutter and React Admin involves classifying the issue scope and impact, then applying guided evidence gathering with concrete checks. This disciplined, repeatable process accelerates incident resolution and learning.

Can I use this structured debugging workflow for database and infrastructure issues?▼

Yes, this workflow supports database and infrastructure issues by guiding you through classification, evidence gathering, and hypothesis verification. It applies to development, staging, and production environments across the entire Scrips stack.

How does evidence-based root cause analysis work during on-call troubleshooting?▼

Evidence-based root cause analysis works by gathering concrete artifacts, forming documented hypotheses, and verifying them systematically. During on-call troubleshooting, this process implements clear escalation and documentation requirements to reduce guesswork.

Why does my debugging process lack repeatability when diagnosing development issues?▼

Your debugging process lacks repeatability without a structured, evidence-based workflow. Implementing a disciplined process with concrete steps, templates for hypotheses, and clear documentation ensures reproducible fixes for development issues.