Ticket Triage and Routing
Skill2 starsChanged 4 months agoMITView on GitHub
Evaluate incoming user support tickets and route them to the proper department.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Academic Paper SummarizationSkill
- Accessibility WCAG AuditSkill
- API Error TroubleshootingSkill
- CI/CD Pipeline TroubleshootingSkill
- Competitor Analysis SynthesisSkill
- Customer Onboarding AssistanceSkill
- Dependency Audit ResolutionSkill
- Docker Image OptimizationSkill
- GDPR Data MappingSkill
- genome-analyzerSkill
- incident-distillerSkill
- Kubernetes Pod DebuggingSkill
- nve-genome-explorerSkill
- OWASP Input ValidationSkill
- repo-auditorSkill
- research-packagerSkill
- rule-patcherSkill
- Secret Leak RemediationSkill
- skill-curatorSkill
- skill-package-builderSkill
- SOC2 Policy VerificationSkill
- tama-community-summarizerSkill
- Technology Stack EvaluationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
When operating in the support domain.
- Distinctive: line 14
When resolving incidents related to ticket triage and routing.
- Distinctive: line 17
If the issue requires manual human intervention.
- Distinctive: line 18
If the domain does not apply.
- Distinctive: line 29
Read the support ticket to extract key entities: user ID, error code, and affected feature.
- Very specific: line 35
If it's a billing issue, route to billing.
- Distinctive: line 48
Always verify changes in a staging environment before applying to production.
- Distinctive: line 49
Do not execute destructive commands without explicit authorization.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ticket Triage and Routing
Evaluate incoming user support tickets and route them to the proper department.
When to use
- When operating in the
supportdomain. - When resolving incidents related to ticket triage and routing.
When not to use
- If the issue requires manual human intervention.
- If the domain does not apply.
Triggers
- Pattern:
ticket-triage - Keywords: support, ticket
Inputs
- Context from the current user session or incident report.
Steps
1. Step 1
Read the support ticket to extract key entities: user ID, error code, and affected feature.
2. Step 2
Determine the severity: P1 (System Down), P2 (Major Bug), P3 (Minor Bug), P4 (Feature Request).
3. Step 3
If it's a billing issue, route to billing. If technical, route to engineering.
4. Step 4
Draft a polite acknowledgment message to the user confirming receipt and priority.
Success signals
- The task is resolved without regressions.
- Logs confirm the procedure was successfully applied.
Failure modes
- Incorrect application of the steps leading to side effects.
Safety notes
- Always verify changes in a staging environment before applying to production.
- Do not execute destructive commands without explicit authorization.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

