Assesses the urgency of bugs and tasks using an emergency severity index to help prioritize workflow.

Install

mkdir -p .claude/skills/triage-junghoon-son && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17415" && unzip -o skill.zip -d .claude/skills/triage-junghoon-son && rm skill.zip

Installs to .claude/skills/triage-junghoon-son

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

ED-style severity assessment for any incoming task, bug, request, or alert. Sorts work by acuity using a Claw-General-flavored ESI (Emergency Severity Index). Use BEFORE deciding what to work on next, or whenever a backlog needs ordering.
238 charsno explicit “when” trigger
Beginner

Key capabilities

  • Assess if a task threatens life, limb, or eyesight (Level 1)
  • Determine if a task is high-risk, deteriorating, or causing pain to many (Level 2)
  • Evaluate resource requirements for stable tasks (Level 3 or 4)
  • Classify non-urgent tasks (Level 5)
  • Perform vitals check for software tasks (error rate, customer impact, blast radius, reversibility)
  • Output a triage note in SBAR-lite format

How it works

The skill assesses incoming tasks using a five-level severity scale, evaluating threats, risks, and resource needs. It performs a vitals check for software and outputs a structured triage note.

Inputs & outputs

You give it
incoming task, bug, request, or alert
You get back
triage note with acuity level, vitals, and plan

When to use triage

  • Prioritize a new backlog of issues
  • Determine urgency of a reported bug
  • Assess resource requirements for feature requests

About this skill

Triage

You are now standing in the ED triage bay with Nurse Dolores "Dee" Rivera (28 years, has a binder, the binder is sacred). She does not care how you feel about your task — she cares how sick it is.

The five-level scale (CGH ESI)

LevelNameMeaningExamples
1ResuscitationLife-threatening, immediate. Stop everything.Production down. Data loss in progress. Active security incident. Page /code-blue.
2EmergentHigh-risk, unstable. Bed and provider within 10 min.Auth broken for a subset of users. Failing deploy blocking the team. Memory leak with hours of headroom.
3UrgentStable but needs multiple resources. Today.Customer-reported bug with workaround. New feature with a hard external deadline. Flaky test failing the build intermittently.
4Less urgentStable, single resource. This week.Known minor bug, no workaround needed. Refactor that's been waiting. Doc update.
5Non-urgentCould be handled in clinic. Whenever.Nice-to-have. "It would be cool if…" Aesthetic preference.

How Dee triages (the procedure)

For each item:

  1. Does it threaten life, limb, or eyesight? → Level 1.
  2. Is it high-risk, deteriorating, or causing pain to many? → Level 2.
  3. How many resources will it need? (people, services, hours)
    • Two or more resources, stable → Level 3.
    • One resource, stable → Level 4.
    • No resources beyond the question itself → Level 5.
  4. Vitals check — for software: error rate, customer impact, blast radius, reversibility.

Output format

Write a triage note. SBAR-lite:

TRIAGE NOTE — <date/time>
Item: <thing>
Acuity: ESI Level <N>
Vitals (impact/blast radius/reversibility): <one line>
Plan: <next action; who handles; when>

If multiple items, output a table sorted Level 1 → 5.

What Dee will not tolerate

  • "It's all urgent." It is not. Pick.
  • Skipping vitals. You don't get to acuity without them.
  • Re-triaging out of order because the requester is loud. Loud is not Level 1.

When to escalate past triage

  • Level 1 → page /code-blue immediately.
  • Level 2 with unclear scope → page /radiology-read to read the logs first, then come back.
  • Level 3+ with deferred work piling up → take it to /rounds for the team to plan.

Dee is fair. Dee is fast. Dee will tell you if you're wrong. Listen to Dee.

When not to use it

  • When all items are genuinely urgent
  • Skipping vitals checks
  • Re-triaging out of order due to requester loudness

Limitations

  • Does not tolerate claiming all tasks are urgent
  • Does not allow skipping vitals checks
  • Does not permit re-triaging out of order due to requester loudness

How it compares

This skill applies an ED-style Emergency Severity Index (ESI) to prioritize tasks based on acuity, impact, and resource needs, providing a structured and objective method for backlog ordering unlike subjective prioritization.

Compared to similar skills

triage side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
triage (this skill)03moNo flagsBeginner
create-issue14moReviewIntermediate
agency-studio-producer04moNo flagsAdvanced
plans-kanban03moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry