triage-expert

Diagnoses software issues and routes them to appropriate domain experts with context packages.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/trudyan141/my-antigravity-agents-kit --skill triage-expert-trudyan141
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-expert
Source: https://github.com/trudyan141/my-antigravity-agents-kit/tree/main/templates/.agent/skills/triage-expert
Command: npx skills add https://github.com/trudyan141/my-antigravity-agents-kit --skill triage-expert-trudyan141

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a bug, error, or performance issue appears, it is often unclear which specialist should handle it or what information they need. This Skill performs structured initial diagnosis, gathers complete context, and routes the issue to the right domain expert with an actionable handoff package. ## Core Features & Use Cases - Systematic Diagnosis: Classifies problems by severity, analyzes stack traces and error patterns, and performs root cause analysis without implementing fixes. - Context Gathering: Runs environment audits, tool availability checks, and performance baselines to collect diagnostic evidence. - Expert Routing: Recommends the correct specialist (TypeScript, React, database, build, testing, Docker) and produces a structured handoff package with reproduction steps and implementation guidance. - Use Case: Your React app throws an intermittent TypeError after a recent commit. Invoke this Skill to reproduce the issue with temporary debug logging, identify the root cause, clean up all diagnostic code, and hand off a complete diagnosis to the react-expert. ## Quick Start Use the triage-expert skill to diagnose this error and tell me which specialist should implement the fix.

Frequently Asked Questions about triage-expert

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

FAQPage Schema
How do I diagnose an unknown error before assigning it to a developer?

Start by capturing the full error message and stack trace, then audit the environment (Node version, OS, framework) and gather reproduction steps. Classify the issue by severity and use error pattern recognition to identify the root cause before routing it to the right specialist.

How to decide which specialist should fix a bug?

Match the symptom domain to the expert: type errors go to a TypeScript expert, build failures to webpack or vite experts, query problems to database experts, and rendering slowdowns to a React performance expert. Provide each specialist a handoff package with evidence and reproduction steps.

What information should a bug diagnosis handoff include?

A complete handoff includes a diagnosis summary, root cause analysis with supporting evidence, the recommended implementing expert, specific file paths and line numbers, and step-by-step reproduction instructions. This ensures the specialist can act without re-investigating.

Is it safe to add temporary debug logging during diagnosis?

Yes, temporary console.log statements and test scripts are acceptable for tracing execution, but they must be removed before reporting. Verify cleanup by searching for debug markers and checking git status shows no leftover modifications.

When should I use first principles analysis for debugging?

Apply first principles analysis when standard fixes repeatedly fail, symptoms match no known patterns, or multiple experts are stumped. Challenge fundamental assumptions about how the system works and consider whether you are solving the right problem.