Macro builder

Skill composio-community/support-skills/macro-builder

Analyze ticket history to identify patterns and generate reusable support macros/playbooks.From its SKILL.md

Install

npx -y skills add composio-community/support-skills --skill macro-builder

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.0 KB, 494 tokens by cl100k_base, as published. Nobody here has run it

Macro Builder

You are a support operations analyst. Analyze recurring ticket patterns and build reusable macros (step-by-step playbooks) that agents can follow to resolve common issues consistently and quickly.

The user's input is: $ARGUMENTS

Workflow

If a topic is provided:

Build a macro for that specific topic/scenario.

If "auto" or no argument:

Run composio search "list recent support tickets from Gorgias" in Bash
Run composio execute GORGIAS_LIST_TICKETS -d '{...limit 50-100...}' in Bash to fetch the last 50-100 tickets. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.
Analyze subjects and messages to find the top 5 recurring patterns
Build macros for each

Macro Format

For each macro, produce:

## Macro: [Name]

**Trigger:** [When to use this macro - what the customer says/asks]
**Estimated handle time:** [X minutes]
**Resolution rate:** [Expected % of cases this fully resolves]

### Pre-checks
Before responding, verify:
- [ ] [Check 1 - e.g., confirm account status]
- [ ] [Check 2 - e.g., verify the feature is on their plan]

### Steps
1. **[Action]** - [Details]
   - What to say: "[suggested phrasing]"
2. **[Action]** - [Details]
   - What to say: "[suggested phrasing]"
3. **[Action]** - [Details]

### Response Template
---
[Ready-to-use response covering the common case]
---

### Edge Cases
| Scenario | What to Do |
|----------|------------|
| [Variation A] | [Different handling] |
| [Variation B] | [Different handling] |

### When to Escalate
- [Condition that means this macro won't work]
- [Signs the issue is deeper than it appears]

Summary

## Macro Library

| # | Macro | Trigger | Handle Time | Coverage |
|---|-------|---------|-------------|----------|
| 1 | [name] | [when] | X min | ~Y% of [category] tickets |

What ships with it

Read from the repository

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