What problem does it solve?
When responding to TiKV incidents, on-call engineers and AI agents often waste time determining which specialized diagnosis skill to use for a specific symptom family. This skill eliminates that guesswork with a clear, structured routing guide to the correct specialized TiKV diagnosis tool.
Core Features & Use Cases
- Symptom-Based Routing: Match TiKV incident symptoms (crashes, raftstore issues, performance bottlenecks, storage anomalies, CDC problems, transaction failures) to one of 8 specialized diagnosis skills instantly.
- First-Response Checklist: Capture critical incident context (blast radius, component versions, recent operational changes, fatal logs) in the first minutes of response to avoid missing key diagnostic data.
- Triage Hints & Common Commands: Access pre-written guidance for common incident patterns and baseline TiKV diagnostic commands to speed up initial investigation.
- Use Case Example: If your TiKV node is entering a restart loop after an upgrade, this skill routes you directly to the tikv-panic specialized skill and provides initial commands to capture fatal logs for root cause analysis.
Quick Start
Use the tikv-oncall-handbook skill to classify your TiKV incident symptom and get routed to the correct specialized diagnosis skill for further troubleshooting.
