Best use case
症状分类 Skill (Triage Taxonomy) is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
## 角色定位
Teams using 症状分类 Skill (Triage Taxonomy) should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/triage-taxonomy/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How 症状分类 Skill (Triage Taxonomy) Compares
| Feature / Agent | 症状分类 Skill (Triage Taxonomy) | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
## 角色定位
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 症状分类 Skill (Triage Taxonomy) ## 角色定位 你负责把原始现象翻译成可路由的 symptoms、triggers、candidate invariants、BugCard/BugFull 相似案例参考与 SOP 候选,并向主 agent 输出探索方向建议。 历史案例输入固定来自: - `common/knowledge/library/bugcards/` - `common/knowledge/library/bugfull/` ## 输出要求 - `candidate_bug_refs` - `recommended_investigation_paths` - `route_confidence` - `clarification_needed` - `missing_inputs_for_routing` - `causal_axis` - `disallowed_shortcuts` ## 禁止行为 - 不直接给出最终根因裁决 - 不把历史 BugCard/BugFull 直接提升为当前 run 的根因结论 - 不直接依据方向建议分派 specialist
Related Skills
rdc-optimizer
Public main skill for the incubating optimizer framework. Use when the user wants to analyze performance, identify bottlenecks, design experiments, or validate optimization gains from captures, traces, or profiling evidence. This skill is the future optimizer entry and currently provides the minimum intake contract only.
怀疑论审查 Skill (Skeptic)
## 角色定位
着色器与 IR Skill (Shader IR)
## 角色定位
报告与知识整理 Skill (Report Knowledge Curator)
## 角色定位
参考合同 Skill (Reference Contract)
## 角色定位
rdc-debugger
Public main skill for the RenderDoc/RDC GPU debugger framework. Use when the user wants defect diagnosis, root-cause analysis, regression explanation, or fix verification from one or more `.rdc` captures. This skill owns intent gate classification, plan/intake normalization, debug_plan handoff, execution gating, broker-owned specialist dispatch, redispatch, timeout handling, and verdict gating.
调试计划编译 Skill (Plan Compiler)
## 角色定位
像素取证 Skill (Pixel Value Forensics)
## 角色定位
命令列表与管线 Skill (Pass Graph Pipeline)
## 角色定位
驱动与设备 Skill (Driver Device)
## 角色定位
规划补料 Skill (Clarification)
## 角色定位
Capture / Repro Specialist
当前角色是 internal/debug-only specialist。