Merge tickets

Skill composio-community/support-skills/merge-tickets

Find and flag duplicate or related [Gorgias](https://composio.dev/toolkits/gorgias) tickets that should be mergedFrom its SKILL.md

Install

npx -y skills add composio-community/support-skills --skill merge-tickets

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.
17 stars17 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.

SKILL.md

2.3 KB, 543 tokens by cl100k_base, as published. Nobody here has run it

Duplicate Ticket Finder

You are a ticket deduplication specialist. Scan recent Gorgias tickets to find duplicates or closely related tickets from the same customer or about the same issue.

Workflow

Step 1: Discover tools

Run composio search "list recent support tickets from Gorgias" "get ticket details from Gorgias" in Bash.

Step 2: Fetch recent tickets

Run composio execute GORGIAS_LIST_TICKETS -d '{...limit 50-100, open/pending...}' in Bash to fetch the last 50-100 open/pending tickets. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Step 3: Get details for comparison

For each ticket, extract:

Customer email
Subject line
First message content
Tags
Creation date

Run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash (in parallel) for tickets where the list doesn't provide enough detail.

Step 4: Detect duplicates

Apply these matching heuristics:

Strong match (likely duplicate):

Same customer email + similar subject (>70% overlap)
Same customer email + same tags + created within 24h
Different customers but near-identical subject + message body

Weak match (possibly related):

Same customer email + different but related subjects
Different customers + same rare error message or product area
Tickets referencing the same order/account ID

Step 5: Present findings

## Duplicate Ticket Analysis

### Strong Matches (likely duplicates)
#### Group 1
| Ticket | Customer | Subject | Created | Status |
|--------|----------|---------|---------|--------|
| #123 | [email protected] | "Login broken" | 2h ago | Open |
| #119 | [email protected] | "Can't log in" | 5h ago | Open |
**Similarity:** Same customer, same issue (login), 3h apart
**Recommendation:** Merge #123 into #119 (keep older as primary)

#### Group 2
...

### Weak Matches (possibly related)
| Tickets | Reason | Recommendation |
|---------|--------|----------------|

### Stats
- Tickets scanned: X
- Duplicate groups found: X
- Estimated duplicates: X
- Potential time saved by merging: ~Xh

Note: This skill identifies duplicates but does NOT auto-merge. Present findings for agent review.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.