rca
Root cause analysis workflows - systematic investigation of failures
Profile →npx skills add majiayu000/claude-skill-registry --skill rca --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
```mermaid flowchart TD FAIL([Failure]) --> RCA{"/rca"} RCA -->|CI failure, no cluster| RCACI["rca:ci"]:::rca RCA -->|HyperShift available| RCAHS["rca:hypershift"]:::rca RCA -->|Kind available| RCAKIND["rca:kind"]:::rca RCACI -->|Inconclusive| NEED{"Need cluster?"} NEED -->|Yes| RCAHS NEED -->|Reproduce locally| RCAKIND RCACI --> ROOT[Root Cause Found] RCAHS --> ROOT RCAKIND --> ROOT ROOT --> TDD["tdd:*"]:::tdd classDef rca fill:#FF5722,stroke:#333,color:white classDef tdd fill:#4CAF50,stroke:#333,color:white ``` > Follow this diagram as the workflow. # RCA Skills Root cause analysis workflows for systematic failure investigation. ## Auto-Select Sub-Skill When this skill is invoked, determine the right sub-skill based on context: ### Step 1: Determine what's available Check for HyperShift cluster: ```bash ls ~/clusters/hcp/kagenti-hypershift-custom-*/auth/kubeconfig 2>/dev/null ``` Check for Kind cluster: ```bash kind get clusters 2>/dev/null ``` ### Step 2: Route based on failure source and access ``` Where did the failure occur? │ ├─ CI pipeline (GitHub Actions) ─────────────────────────┐ │ │ │ Do you have a live cluster matching the CI env? │ │ │ │ │ ├─ HyperShift cluster availa
- Auto-Select Sub-Skill
- Step 1: Determine what's available
- Step 2: Route based on failure source and access
- Available Skills
- Related Skills
ls ~/clusters/hcp/kagenti-hypershift-custom-*/auth/kubeconfig 2>/dev/null kind get clusters 2>/dev/null
What does the rca skill do?
Root cause analysis workflows - systematic investigation of failures
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill rca --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.