Skip to content
Back to skills

Macro Builder

ASecurity

Analyze ticket history to identify patterns and generate reusable support macros/playbooks.

  • 18 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 27, 2026
data-aigobash

Works with

  • cli

Security analysis

A100/100

Scanned May 27, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Macro Builder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Macro Builder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/composio-community-macro-builder/badge)](https://www.skillsdirectory.com/skills/composio-community-macro-builder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: macro-builder
description: Analyze ticket history to identify patterns and generate reusable support macros/playbooks.
disable-model-invocation: true
argument-hint: "[topic or 'auto']"
---

# 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:
1. Run `composio search "list recent support tickets from Gorgias"` in Bash
2. 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.
3. Analyze subjects and messages to find the top 5 recurring patterns
4. 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 |
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.