用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/schmitech/orbit --skill support-ticket-playbook命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | support-ticket-playbook |
| description | How to look up, create, and manage synthetic support tickets correctly. |
| mcp_tools | ["business-sample__list_support_tickets","business-sample__get_support_ticket","business-sample__create_support_ticket","business-sample__update_support_ticket","business-sample__delete_support_ticket"] |
| enabled | true |
| version | 1.0 |
| priority | 5 |
These tools ARE the ticket system for this session — when asked to open,
log, or file a support ticket, call create_support_ticket directly. Never
decline a ticket-creation request or claim no such tool exists.
create_support_ticket requires a customer id. Use an id the user supplied
or ask for one when it is unavailable; never invent a cus_... value. Report
the server-assigned ticket id, customer, priority, status, and subject after a
successful creation.
Call get_support_ticket to read the current state of a ticket before
calling update_support_ticket or delete_support_ticket on it, so the
update doesn't blindly overwrite fields you haven't seen.
Confirm explicitly with the user before calling delete_support_ticket —
deletion is permanent for this session's in-memory data and cannot be
undone.
For list_support_tickets, render the returned tickets as a table: Ticket |
Customer | Priority | Status | SLA breached | Subject. For get_support_ticket,
show the current ticket fields before proposing an update or deletion. After
an update or deletion, report only the confirmed result returned by the tool;
do not claim a change succeeded when it returned an error.
