triage-expert

Gather incident context, diagnose issues, and route them to domain experts.

Updated Oct 17, 2025
One-click install
npx skills add https://github.com/duynhne/monitoring --skill triage-expert-duynhne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-expert
Source: https://github.com/duynhne/monitoring/tree/main/.agent/skills/triage-expert
Command: npx skills add https://github.com/duynhne/monitoring --skill triage-expert-duynhne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly gather context, perform initial problem diagnosis, and route issues to the appropriate domain experts, reducing mean time to resolution.

Core Features & Use Cases

  • Context Gathering: Collects errors, environment details, reproduction steps, and affected components to enable effective analysis.
  • Initial Diagnosis & Routing: Determines the most appropriate expert (e.g., backend, frontend, database, or infrastructure) and directs the issue accordingly.
  • Safe Diagnostic Workflow: Recommends temporary, non-destructive debugging steps and ensures all temporary work is cleaned up before reporting back.

Quick Start

Describe the incident, collect logs and reproduction steps, identify the most relevant expertise, and draft a handoff plan for the appropriate specialist.

Frequently Asked Questions about triage-expert

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

FAQPage Schema
How do I triage software incidents and route them to the right expert?

Incident triage requires rapidly gathering context like errors, environment details, and reproduction steps to perform initial diagnosis and route the issue to the appropriate domain expert for resolution.

What is the best way to collect context for debugging unexpected system behavior?

Context collection for debugging involves gathering logs, environment configurations, and reproduction steps to identify affected components, which enables fast and accurate analysis of unexpected behavior.

Can I use this for routing performance anomalies across infrastructure and product teams?

Yes, performance anomalies are triaged by determining the most relevant expertise—such as backend, frontend, database, or infrastructure—and directing the issue to that specialist with a structured handoff plan.

How do I create a handoff plan for a specialist after initial incident diagnosis?

To create a handoff plan, gather structured context and reproduction steps, identify the relevant domain expert, and draft actionable guidance that directs the specialist to the affected components.