support-macro-library

$npx mdskill add Significant-Gravitas/skills-catalog/support-macro-library

Use this when the same answer goes out by hand again and again.

SKILL.md

.github/skills/support-macro-libraryView on GitHub ↗
---
name: "support-macro-library"
description: "Turn repeated answers into reusable macros with placeholders, scope, and the tickets they came from."
triggers: ["support macros", "canned responses", "saved replies", "reply templates", "repeat answers"]
version: "1"
---

# Support macro library

Use this when the same answer goes out by hand again and again.

## Find repeat answers

Search sent replies and closed tickets for answers that share the same steps
or wording. Count how often each one went out, over what period, and cite the
ticket ids. Check each answer against the current help centre and product
notes; drop any that no longer match.

## Write the macro

For each macro give:

- a short name agents can search for;
- the question it answers, in the customer's words;
- the reply, with `{placeholders}` for name, plan, dates, and links;
- the source article or note that confirms each step;
- the tags or fields the macro should set, if the team uses them.

Keep one macro to one question. Write in the team's agreed tone.

## When not to use it

For each macro, state the cases where it does not fit: other plans, known
bugs, angry or legal threads, refunds, or anything the source does not cover.
Name the person who owns keeping it current.

Do not add macros to the help desk yourself; draft them for approval. Never
put a step, limit, or policy in a macro that no source confirms.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.