ticket-routing

仓库创建 2026年7月2日最近提交 21 天前SkillHot 收录 20 天前

▸ 精选理由

无LLM、可复现的路由规则，适合运维与客服自动化

这个 Skill 做什么

根据优先级、安全评分和客户属性将工单路由到合适队列

把工单的优先级、安全评分、客户等级、分类和是否违约等信息结构化，然后一致性地分到 human_review、escalate_security、escalate_urgent、route_billing、route_engineering 或 route_default 这类队列。适合在必须可审计、结果固定的场景使用，比如合规或有审计需求的自动路由。特别之处是决策是冻结的、由版本控制的决策树（route_ticket）判断，不用 LLM，别改它的结论，只负责把数据喂进去并传达裁决。

▸ 展开 SKILL.md 英文原文

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.

自动化集成工单路由优先级安全分流审计通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/CyrilLeMat/temper-skills/main/examples/ticket_routing/output/ticket-routing/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/CyrilLeMat/temper-skills/main/examples/ticket_routing/output/ticket-routing/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# 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

1. 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`):

   ``

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有