huawei-cloud-cce-root-cause-analyzer

What problem does it solve? When a CCE incident spans alarms, workload rollouts, Pod events, nodes, network, and storage, engineers struggle to correlate scattered signals into a single root cause. This Skill converges multi-domain evidence into ranked root cause conclusions with confidence scores and a customer-ready Markdown report. ## Core Features & Use Cases - Cross-domain evidence orchestration: Collects read-only evidence through hcloud, kubectl cce, and focused domain diagnoser skills (workload, pod, node, network, storage, change, dependency impact). - Ranked root cause analysis: Builds a unified incident timeline and ranks Top3 causes by timeline alignment, evidence strength, blast radius, counter-evidence, and recoverability. - Structured reporting: Outputs a Markdown report with Summary, Root Cause Analysis, Next Actions, Evidence Timeline, Impact Scope, and data gaps, plus a JSON output schema. - Use Case: A Deployment rollout stalls while AOM alarms fire and Pods enter CrashLoopBackOff. The Skill gathers cluster state, events, and change history, then identifies the failing image pull as the top cause with supporting evidence and verification steps. ## Quick Start Analyze the ongoing incident in my CCE cluster in region cn-north-4 for cluster ID <cluster-uuid> affecting namespace production and rank the most likely root causes.