ticket-management
Skill0 starsChanged 3 months agoMITView on GitHub
创建、更新、升级与关闭 IT 工单。当需要提交工单或无法自动解决时使用。
In this repository8 other files it gives its agents.
- account-accessSkill
- escalationSkill
- pdfSkill
- office-applicationSkill
- onedrive-syncSkill
- outlook-troubleshootingSkill
- resolution-reportSkill
- teams-troubleshootingSkill
The file
Files
Ticket Management Skill
- 汇总已有诊断上下文（账号、设备、文档依据）
- 仅当尚无工单时
create_ticket（完整 title/description/category/priority/employee_id）- 同一 title+employee 已创建过 → 勿再 create；用返回的
ticket_id继续 create_ticket需 HITL 批准后才落库
- 同一 title+employee 已创建过 → 勿再 create；用返回的
- 调整优先级 / 处理人：
update_ticket(ticket_id, priority="P3")（勿把 P1–P4 写入 status） - 升级：
check_action_permission("escalate_ticket")→escalate_ticket(ticket_id, reason)- 禁止在已有
ticket_id时再调create_ticket - 不要与 create 同批调用
- 禁止在已有
- 关闭：
check_action_permission("close_ticket")→close_ticket（需审批）
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.