skills.rest
ginaecho
ginaechoCOMMUNITY
Explore all skills by this author →
GitHub

triage-then-handle

Routes support tickets through triage to simple or complex resolution paths.

1|Updated Jul 1, 2026
Search Tags:#workflow#routing#triage#support tickets#contract#resolution#handler
One-click install
npx skills add https://github.com/ginaecho/skill-achievability-compiler --skill triage-then-handle-ginaecho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-then-handle
Source: https://github.com/ginaecho/skill-achievability-compiler/tree/main/corpus/skills/conformant_tolerant_handler
Command: npx skills add https://github.com/ginaecho/skill-achievability-compiler --skill triage-then-handle-ginaecho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Support tickets often need triage before a handler can resolve them, and without a clear routing contract tickets can be misrouted or left unresolved. This Skill defines a two-participant workflow where a router classifies each ticket and a handler resolves it on the appropriate path. ## Core Features & Use Cases - Two-path triage contract: A router inspects each ticket and sends either go_simple or go_complex to the handler. - Deterministic resolution: The handler marks tickets resolved using resolve_simple or resolve_complex depending on the received label. - Tolerant handler design: The handler also accepts an unused go_escalate label, safely covering more cases than the router will ever send. - Use Case: A support team wants incoming tickets automatically classified as simple or complex so each one is resolved with the correct tool without manual routing. ## Quick Start Triage this support ticket and resolve it using the simple or complex path as appropriate.

Frequently Asked Questions about triage-then-handle

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

FAQPage Schema
How do I triage support tickets before resolving them?▼

Use a router participant that inspects each ticket and sends a go_simple or go_complex label to a handler. The handler then resolves the ticket with resolve_simple or resolve_complex based on the label it receives.

What is a tolerant handler in a ticket routing contract?▼

A tolerant handler accepts more message labels than the router will ever send. Here the handler is prepared for go_escalate even though the contract only sends go_simple or go_complex, which is safe because every actual router path is still covered.

Can a handler support escalation paths the router never uses?▼

Yes. Being ready for extra labels like go_escalate does not break the contract, since the handler still covers every path the router can actually take. The unused branch simply never triggers in practice.

When is a ticket considered resolved in this workflow?▼

A ticket is resolved when the handler calls resolve_simple or resolve_complex after receiving a routing label. The job is finished only once the ticket reaches the resolved state.

Related Skills

Explore More Software Engineering Skills→
73ai73ai
4

persona-customer-support

Triage support emails, convert them to tasks, and update ticket statuses.

Official
Intermediate
augustoheissaugustoheiss

agency-feedback-synthesizer

Synthesize multi-channel user feedback into prioritized product insights.

Community
Advanced
saolalabsaolalab
37

ticket-management

Create and manage support tickets through triage, assignment, and SLA tracking.

Official
Intermediate
teradata-labsteradata-labs
7

td-decision-tree

Automate TD_DecisionTree classification model creation and deployment in Teradata Vantage.

Official
Advanced