Root cause

Skill composio-community/support-skills/root-cause

Customer support skills for Claude Code and AI agents. Ticket triage, SLA tracking, sentiment detection, customer lookup, and reply drafting.

Install

npx -y skills add composio-community/support-skills --skill root-cause

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze a set of related tickets to identify the underlying root cause.

SKILL.md

2.8 KB, as published. Nobody here has run it

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:

Run composio search "get ticket details from Gorgias" in Bash
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.
Analyze the cluster

If a topic/keyword is provided:

Run composio execute GORGIAS_LIST_TICKETS -d '{...keyword filter...}' in Bash to search for related tickets
Run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash (in parallel) to fetch details for matches
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

Starting from the symptom, ask "why" five times to drill down:

Symptom: [What customers are reporting]
Why 1: [First level cause]
Why 2: [Deeper cause]
Why 3: [Even deeper]
Why 4: [Getting to root]
Why 5: [Root cause]

3. Impact Assessment

How many customers are affected?
What's the revenue impact?
Is it getting worse or stable?
Is there a workaround?

Output

## Root Cause Analysis

### Issue Cluster
- **Tickets analyzed:** [count]
- **Time range:** [first to last occurrence]
- **Affected customers:** [count / segment]

### Symptom
[What customers are seeing/reporting]

### Root Cause
[The actual underlying issue - be specific]

### Five Whys Chain
1. Customers report [symptom]
2. Because [why 1]
3. Because [why 2]
4. Because [why 3]
5. Because [why 4] <- ROOT CAUSE

### Evidence
| Data Point | Finding |
|------------|---------|
| [source] | [what it tells us] |

### Impact
- Customers affected: X
- Ticket volume from this issue: X
- Estimated revenue impact: $X
- Trend: [Growing / Stable / Declining]

### Recommendations
| Priority | Action | Owner | Impact |
|----------|--------|-------|--------|
| P0 | [Fix the root cause] | Engineering | Eliminates X tickets/week |
| P1 | [Add monitoring] | DevOps | Early detection |
| P2 | [Update KB article] | Support | Reduce handle time |

### Workaround (for now)
[Steps agents can give customers until the fix ships]