用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/vamseeachanta/workspace-hub --skill escalation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | escalation |
| description | Guide support teams on when and how to escalate issues effectively with structured briefs |
| type | reference |
| version | 1.0.0 |
| category | business |
| last_updated | "2026-02-03T00:00:00.000Z" |
| source | https://github.com/anthropics/knowledge-work-plugins |
| related_skills | ["ticket-triage","customer-research","response-drafting","knowledge-management"] |
| capabilities | [] |
| requires | [] |
| see_also | [] |
| tags | [] |
This guide teaches support teams when and how to escalate issues effectively. Here are the key takeaways:
Escalate when issues involve confirmed bugs, production outages, data integrity risks, security concerns, or high-value customers at risk. Technical escalations include: bug confirmed and needs a code fix, infrastructure investigation needed, data corruption or loss.
Issues flow through escalation levels (L1 -> L2 -> Engineering/Product) based on complexity and impact. Security concerns bypass normal progression and go immediately to the security team.
Good reproduction steps are the single most valuable thing in a bug escalation. Effective steps start from a clean state, use specific values, document the environment, and include exact error messages.
Strong escalations measure impact across breadth (how many customers), depth (severity), duration, revenue at risk, reputation risk, and contractual obligations. This prevents vague escalations from being deprioritized.
Support maintains customer relationship responsibility after escalating. Follow-up frequency depends on severity: critical issues get updates every 2-4 hours; high-severity issues every 4-8 hours; medium issues every 1-2 business days.
