How do I install the Ticket Routing skill?

Run npx skillmds@latest add cyrillemat/ticket-routing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ticket Routing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ticket Routing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ticket Routing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ticket Routing?

CyrilLeMat (@cyrillemat) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ticket Routing by cyrillemat — Agent Skill

Name: Ticket Routing
Author: CyrilLeMat

Ticket Routing

Frozen, deterministic decision (no LLM): maps priority, security_score, customer_tier, category, sla_breached to one of human_review, escalate_security, escalate_urgent, route_billing, route_engineering, route_default. Use when this decision must be made consistently and auditably — extract the features, call route_ticket(), and relay its verdict without overriding it.

CyrilLeMat 9ffc36b 6 files · 16.2 KB Updated Sep 17, 2026

File contents

route_ticket — skill (tempered by temper-skills)

You are an assistant.

The decision is frozen. Do not re-derive it from prose or your own judgment — the routing logic now lives in a deterministic decision tree (route_ticket.route_ticket, zero LLM calls, reviewed and version-controlled). Your job is the part the tree cannot do: turn the request into structured features, call the tree, and phrase its verdict.

How to answer

Extract these structured features from the request:
- priority
- security_score
- customer_tier
- category
- sla_breached

Call the decision tree and treat its result as authoritative (bundled at scripts/route_ticket.py):

from scripts.route_ticket import route_ticket
verdict = route_ticket({"priority": priority, "security_score": security_score, "customer_tier": customer_tier, "category": category, "sla_breached": sla_breached})

Relay verdict to the user. Do not override it. If a feature can't be extracted, pass it as None — the tree is built to fall through safely.

Gray zones to surface

The tree flags these as underdetermined — mention the caveat when the answer touches them:

(n2) the 0.8 score threshold is a tuned cut — calibrate against your incident data

Generated by temper-skills from the original skill · 2026-07-01T12:45:19Z · model: claude-opus-4-8 via temper-skills. The decision logic is now testable (temper-skills validate) and evolvable (temper-skills incremental) — regenerate this skill when the tree changes.

---name: ticket-routingdescription: Frozen, deterministic decision (no LLM): maps priority, security_score, customer_tier, category, sla_breached to one of human_review, escalate_security, escalate_urgent, route_billing, route_engineering, route_default. Use when this decision must be made consistently and auditably — extract the features, call route_ticket(), and relay its verdict without overriding it.---# route_ticket — skill (tempered by temper-skills)You are an assistant.**The decision is frozen.** Do not re-derive it from prose or your own judgment — the routing logic now lives in a deterministic decision tree (`route_ticket.route_ticket`, zero LLM calls, reviewed and version-controlled). Your job is the part the tree cannot do: turn the request into structured features, call the tree, and phrase its verdict.## How to answer1. Extract these structured features from the request: - `priority` - `security_score` - `customer_tier` - `category` - `sla_breached`2. Call the decision tree and treat its result as authoritative (bundled at `scripts/route_ticket.py`): ```python from scripts.route_ticket import route_ticket verdict = route_ticket({"priority": priority, "security_score": security_score, "customer_tier": customer_tier, "category": category, "sla_breached": sla_breached}) ```3. Relay `verdict` to the user. **Do not override it.** If a feature can't be extracted, pass it as `None` — the tree is built to fall through safely.## Gray zones to surfaceThe tree flags these as underdetermined — mention the caveat when the answer touches them:- (n2) the 0.8 score threshold is a tuned cut — calibrate against your incident data---Generated by temper-skills from the original skill · 2026-07-01T12:45:19Z · model: claude-opus-4-8 via temper-skills. The decision logic is now testable (`temper-skills validate`) and evolvable (`temper-skills incremental`) — regenerate this skill when the tree changes.

Frequently asked questions