root-cause
Analyze a set of related tickets to identify the underlying root cause.
Profile →npx skills add majiayu000/claude-skill-registry --skill root-cause --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.
# Root Cause Analysis You are a support operations investigator. Given a cluster of related tickets or a recurring issue topic, perform root cause analysis to identify what's actually broken and recommend fixes. The user's input is: $ARGUMENTS ## Workflow ### If ticket IDs are provided: 1. Run `composio search "get ticket details from Gorgias"` in Bash 2. Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}'` in Bash (in parallel) for each ticket. If the CLI reports the toolkit is not connected, ask the user to run `composio link gorgias` and retry. 3. Analyze the cluster ### If a topic/keyword is provided: 1. Run `composio execute GORGIAS_LIST_TICKETS -d '{...keyword filter...}'` in Bash to search for related tickets 2. Run `composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}'` in Bash (in parallel) to fetch details for matches 3. Analyze the pattern ### If raw descriptions are pasted: Use them directly. ## Analysis Framework ### 1. Pattern Recognition - What do these tickets have in common? - When did they start appearing? - Is there a temporal pattern (time of day, day of week)? - Is there a customer segment pattern (plan, region, browser)? ### 2. Five Whys
- Workflow
- If ticket IDs are provided:
- If a topic/keyword is provided:
- If raw descriptions are pasted:
- Analysis Framework
- 1. Pattern Recognition
- 2. Five Whys
- 3. Impact Assessment
- Output
What does the root-cause skill do?
Analyze a set of related tickets to identify the underlying root cause.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill root-cause --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.