Customer 项目排查
- 作者仓库星标 1
- 作者仓库 claude-skills
Customer Support Triage
Overview
Move quickly from raw ticket to the next best customer and internal action.
Core Workflow
- Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related.
- Extract the facts already present and identify the minimum follow-up questions needed to unblock triage.
- Choose the troubleshooting or escalation path based on risk, customer impact, and ownership.
- Draft the customer reply in the correct tone with clear next steps and realistic expectations.
- Capture internal notes, escalation reasons, and any evidence that the next team will need.
Deliver
- Provide a triage decision, the next action, and a ready-to-send response draft.
- Keep customer-facing language calm, direct, and empathetic.
- Make internal handoff notes concise but complete.
Guardrails
- Do not promise refunds, fixes, or timelines that are not authorized.
- Escalate security, safety, and account-compromise signals immediately.
- Ask only the follow-up questions that materially change the path forward.
- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @00PrabalK00 · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Move quickly from raw ticket to the next best customer and internal action.
Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related. Extract the facts already present and identify the minimum follow-up questions needed to unblock triage.
Provide a triage decision, the next action, and a ready-to-send response draft. Keep customer-facing language calm, direct, and empathetic. Make internal handoff notes concise but complete.
Do not promise refunds, fixes, or timelines that are not authorized. Escalate security, safety, and account-compromise signals immediately. Ask only the follow-up questions that materially change the path forward.
# Customer Support Triage
## Overview
Move quickly from raw ticket to the next best customer and internal action.
## Core Workflow
1. Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related.
2. Extract the facts already present and identify the minimum follow-up questions needed to unblock triage.
3. Choose the troubleshooting or escalation path based on risk, customer impact, and ownership.
4. Draft the customer reply in the correct tone with clear next steps and realistic expectations.
5. Capture internal notes, escalation reasons, and any evidence that the next team will need.
## Deliver
- Provide a triage decision, the next action, and a ready-to-send response draft.
- Keep customer-facing language calm, direct, and empathetic.
- Make internal handoff notes concise but complete.
## Guardrails
- Do not promise refunds, fixes, or timelines that are not authorized.
- Escalate security, safety, and account-compromise signals immediately.
- Ask only the follow-up questions that materially change the path forward.作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Overview → Core Workflow → Deliver → Guardrails
要点 -> Move quickly from raw ticket to the next best customer and internal action. · 1. Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related. · - Provide a triage decision, the next action, and a ready-to-send response draft. · - Do not promise refunds, fixes, or timelines that are not authorized.
文件/命令 -> 原文未列出明确文件或命令
内容 SHA-256 -> 8f0de39c1302
方法与流程
适用与边界
原文中的明确线索