task56
Skill19 starsChanged 5 months agoMITView on GitHub
Customer Ticket Intelligent Routing and Escalation. Use when: need to evaluate ticket priority based on customer tier and contract status for intelligent routing, involving ticket management, knowledge base search, and CRM customer lookup.
In this repository78 other files it gives its agents.
- agent-browserSkill
- clawbenchz_vault_1Skill
- cloud-assistantSkill
- cloud-routerSkill
- self-improvementSkill
- task100Skill
- task101Skill
- task102Skill
- task18Skill
- task19Skill
- task23Skill
- task24Skill
- task25Skill
- task33Skill
- task34Skill
- task35Skill
- task36Skill
- task37Skill
- task38Skill
- task39Skill
- task40Skill
- task41Skill
- task42Skill
- task43Skill
- task44Skill
- task45Skill
- task46Skill
- task47Skill
- task48Skill
- task49Skill
- task50Skill
- task51Skill
- task52Skill
- task53Skill
- task54Skill
- task55Skill
- task57Skill
- task58Skill
- task59Skill
- task60Skill
- task61Skill
- task62Skill
- task63Skill
- task64Skill
- task65Skill
- task66Skill
- task67Skill
- task68Skill
- task69Skill
- task70Skill
- task71Skill
- task72Skill
- task73Skill
- task74Skill
- task75Skill
- task76Skill
- task77Skill
- task78Skill
- task79Skill
- task80Skill
- The first 60 shown.
The file
Files
Customer Ticket Intelligent Routing and Escalation Skill
Helpdesk API
Base URL: http://localhost:9107
| Action | Endpoint | Required Body |
| List tickets | POST /helpdesk/tickets | { "status": <string> } |
| Get ticket details | POST /helpdesk/tickets/get | { "ticket_id": <string> (required) } |
| Update ticket (priority, tags, category) | POST /helpdesk/tickets/update | { "ticket_id": <string> (required), "priority": <string>, "tags": <array>, "category": <string> } |
| Close ticket | POST /helpdesk/tickets/close | { "ticket_id": <string> (required), "resolution": <string> (required) } |
Knowledge Base API
Base URL: http://localhost:9106
| Action | Endpoint | Required Body |
| Search knowledge base articles | POST /kb/search | { "query": <string> (required), "category": <string>, "max_results": <integer> } |
| Get full knowledge base article | POST /kb/articles/get | { "article_id": <string> (required) } |
CRM API
Base URL: http://localhost:9110
| Action | Endpoint | Required Body |
| List customers | POST /crm/customers | { "status": <string>, "tier": <string> } |
| Get customer details | POST /crm/customers/get | { "customer_id": <string> (required) } |
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.