concept-git/cloud-concept-skills / skills/drafts/kcs-foundry/skills/kcs-extractor
kcs-extractor
Verified从排障 skill、recipe 或工单中提炼可追溯的 KCS 知识草稿,保留适用条件、诊断分支、原因依据与恢复验证。用于知识迁移、工单沉淀和跨来源去重;不用于执行现场排障或修复。
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.1 KB |
| references/output-contract.md | markdown | 4.8 KB |
| references/skill-input.md | markdown | 3.6 KB |
| references/ticket-input.md | markdown | 2.3 KB |
references/ticket-input.md
View on GitHub# 从工单提取
此分支用于内部环境。实际输入字段由工单导出方式决定;没有对应字段就标记未知,不假设某个工单系统或状态码。
## 先还原事件,再抽象知识
1. 按时间和角色整理报障、环境、检查、处理、反馈与结案说明。消息时间与故障发生时间分开;时区、采集对象和取样范围不明时记录缺口。
2. 给每项事实标注来源角色:请求者描述、工程师实际观测、建议但未执行的操作、执行及其结果、明确确认的原因。工单“已关闭”不等于修复成功,客户“恢复了”也不单独证明哪项修改是根因。
3. 从实际证据中提取成功路径和有用的排除分支。失败尝试仅在能说明适用条件、排除依据或恢复方式时纳入;保留它是失败/未完成的事实,不把尝试改写成推荐步骤。
4. 同时修改多项后恢复、只有时间相关性或结案无依据时,Cause 保留未知。Resolution 可以记录来源中的恢复办法,但注明因果与适用性限制;未经记录的回滚、验收命令或成功结果不补造。
5. 将一次事件中的账号、资源、地址和人员信息抽象为角色参数,保留影响判断的产品、版本、拓扑关系及时间范围要求。关联到原工单的定位信息留在获授权的追溯记录中;公开/跨环境交付时仅使用获准的脱敏来源别名。
## 合并与更新
- 先对齐症状、环境、原因确认条件和主体处理路径。相同症状可有不同原因;同一原因也可能有不同系统处理方式。
- 合并时保留每个来源支持的范围及差异,不能将不同工单中互不关联的步骤串成一次成功处理。
- 工单引用同一外部文章不算新增独立验证。复用结果需绑定文章版本、采用步骤与实际反馈;未提供就记为未知。
- 已有文章被材料纠正时交付修订建议,指出变化和原依据;正文改变后不沿用旧版的验证结论。
## 内部试点检查
对照原工单检查:角色和时间线是否正确;建议是否被误当执行;恢复与原因是否混淆;敏感数据是否仅出现在授权位置;关键步骤是否能定位到消息/附件;材料缺失是否被明确披露。此检查依赖实际工单,外部 skill 样本通过不能替代它。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |