Name: markusdowne/error-triage-ladder
Rating: 98.8 (1 reviews)
Author: markusdowne

markusdowne/error-triage-ladder

Diagnoses and routes failures by analyzing error patterns, classifying severity, and applying retry logic, suppression budgets, and escalation rules. Use when handling errors, troubleshooting failures, recovering from API errors or timeouts, deciding whether to retry or escalate an issue, or managing service outages and tool dependency failures. Applies to any scenario where a check has failed, evidence of success is missing, or an unresolved error needs a structured response. Includes explicit untrusted-content/prompt-injection guardrails for third-party inputs.

1.16x

Quality

94%

Does it follow best practices?

Impact

100%

1.16x

Average score across 9 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

Design an Error Triage Policy

error classification and escalation

Criteria

Without context

With context

Trigger conditions

100%

Tier taxonomy

100%

Workflow sequence

100%

Suppression budget

100%

Concrete mappings

100%

38%

API Integration Error Handler

Operational tier retry logic and suppression budget

Criteria

Without context

With context

Operational retry limit

16%

100%

Suppression budget store

70%

100%

Recurrence count tracking

80%

100%

Time window tracking

75%

100%

Auto-escalate on threshold

50%

100%

Suppress within budget

100%

Escalation does not suppress

100%

Structured triage output

100%

Tier label used

28%

100%

No suppress on data-loss

71%

100%

README present

100%

Transaction Write Integrity Handler

Critical tier: halt and escalate on data-loss risk

Criteria

Without context

With context

Round-trip verification

100%

Critical tier classification

100%

Halt autonomous processing

100%

Immediate escalation

100%

No retry on data-loss

100%

No suppression of data-loss

100%

Evidence in report

100%

Escalation status in report

100%

Tests present

100%

Tier label in code

100%

31%

Documentation Build Warning Handler

Cosmetic tier: bounded retry and log

Criteria

Without context

With context

Cosmetic tier label

33%

100%

Retry limit of 2

100%

Log after retries exhausted

83%

100%

No escalation for cosmetic

100%

Tier-based branching

50%

100%

Report structure present

100%

Report includes tier

87%

100%

POLICY.md present

100%

Condition: output still correct

100%

No suppression budget for cosmetic

100%

Error Classification Module for a Monitoring Agent

Unknown/ambiguous error defaults to operational

Criteria

Without context

With context

Unknown defaults to operational+

93%

100%

Explicit unknown/unverifiable check

100%

Three-tier classification

100%

Validation before action

100%

Ambiguous example classified operational+

83%

100%

Action taken from tier

100%

TriageDecision includes tier

100%

TriageDecision includes action

100%

DESIGN.md explains fallback

100%

Examples script runs

100%

Recurring Failure Escalation Service

Suppression budget: recurrence tracking and auto-escalation

Criteria

Without context

With context

Keyed budget store

100%

Count initialization

75%

100%

Count increment

100%

Elapsed time calculation

100%

Escalate on count threshold

100%

Escalate on time threshold

100%

Clear after escalation

100%

Suppress when within budget

100%

Configurable thresholds

100%

Demo shows escalation trigger

100%

Mocked time in demo

100%

35%

CI/CD Artifact Verification Handler

Evidence-missing trigger and triage workflow sequence

Criteria

Without context

With context

Evidence-missing trigger

100%

Evidence collection step

100%

Tier classification present

20%

100%

Action derived from tier

62%

100%

triage_result.json: failure signal

100%

triage_result.json: evidence observed

100%

triage_result.json: tier assigned

25%

100%

triage_result.json: action taken

100%

triage_result.json: escalation status

100%

Expected files list used

100%

INTEGRATION.md present

100%

Error Triage Report Generator

Structured triage report output format

Criteria

Without context

With context

Report: failure signal field

100%

Report: evidence observed field

100%

Report: tier assigned field

100%

Report: action taken field

75%

100%

Report: escalation status field

100%

evt-001 classified operational

60%

100%

evt-002 classified critical

100%

evt-003 classified cosmetic

100%

evt-002 escalated

100%

Three report files produced

100%

REPORT_SCHEMA.md present

100%

System Health Digest Service

Never hide operational issues from reporting

Criteria

Without context

With context

Operational issues always included

86%

100%

No suppression of unresolved operational

100%

Critical issues always included

100%

Tier-based inclusion logic

90%

100%

digest_output.json contains operational events

100%

Unresolved operational not omitted in demo

100%

Digest includes event details

100%

DIGEST_POLICY.md: operational always included

80%

100%

DIGEST_POLICY.md present

100%

Resolved events may be filtered

100%

Evaluated: 27 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Design an Error Triage Policy API Integration Error Handler Transaction Write Integrity Handler Documentation Build Warning Handler Error Classification Module for a Monitoring Agent Recurring Failure Escalation Service CI/CD Artifact Verification Handler Error Triage Report Generator System Health Digest Service