> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Triage Learnings

> The saved store of triage corrections your techs made, which the category, type and priority skills read first and only the closure review edits.

Runs asAgent Build it with Agent Builder: save this as a shared skill, add the action to a Flow, and choose Run a Skill. It loads other saved skills, so Prompt the Agent can't run it. It runs unattended on a matching ticket event. You can also run it yourself in Super Magic while you prove it out.Works withThreadRole[Service & Ops Manager](https://docs.getthread.com/start-here/roles/service-ops-manager), [Dispatcher](https://docs.getthread.com/start-here/roles/dispatcher)OutcomeFaster Resolution & Response, Fewer Escalations & Less NoiseCategory[Automation & Flows](https://docs.getthread.com/skill-library/automation-and-flows/overview) · [View source ↗](https://github.com/Thread-Magic/super-magic-skills/blob/main/skills/automation-and-flows/triage-learnings/SKILL.md)

**When to use:** You run the Self-Learning Triage Orchestrator (`automation-and-flows/self-learning-triage-orchestrator`) and want its classifications to improve from your techs' corrections without anyone hand-editing prompts. Save this exactly as written, starting empty. Triage Closure Review (`qa-and-closure/triage-closure-review`) fills it in as tickets close.

**Run it:** read at the start of every triage run · edited only by the closure review Flow. Review it weekly and delete any learned rule that looks wrong; each one is a single line, so rolling one back is a one-line delete.

## Prompt

```
Purpose: this desk's learned triage corrections. "Triage Category", "Triage Ticket Type" and "Triage Priority" read this before deciding. Learned rules override their base rules. Only "Triage Closure Review" edits this skill.

HOW TO USE (triage skills)
- If a LEARNED RULE matches the ticket, follow it and say "learned rule L<n>" in your reason.
- Ignore the WATCHLIST when triaging. It is unproven.

LEARNED RULES
(Format: L<n> | Field | When the ticket is about... | Use... | Not... | Evidence: #id, #id, #id | Added YYYY-MM-DD)
- none yet

WATCHLIST
(Format: W<n> | Field | When the ticket is about... | Tech chose... | Agent chose... | Count <n> | High-conf <n> | Tickets | Last seen YYYY-MM-DD)
- none yet

EDITING RULES (for "Triage Closure Review" only)
- Keep this skill under 2,800 characters.
- One line per rule or watchlist item. Describe the ticket pattern as product + problem, never a single keyword.
- To make room: first drop WATCHLIST items with Count 1 not seen in 30 days, then the oldest watchlist items. Never drop a LEARNED RULE to make room. Merge overlapping rules instead.
- Never edit HOW TO USE or EDITING RULES.
```


## Related topics

- [Chain skills into a self-learning triage agent](https://docs.getthread.com/super-magic/chain-skills-into-a-self-learning-triage-agent.md)
- [Triage Agent Setup User Guide](https://docs.getthread.com/ai-agents/setting-up-your-triage-agent-user-guide.md)
- [Claude on AWS Bedrock](https://docs.getthread.com/security-billing/claude-on-aws-bedrock.md)