support-macro
Write reusable support macros / canned responses that sound human, not robotic. Use when asked to write a support macro, a canned response, a saved reply, or a template for a common customer ticket. Produces a macro — an empathetic opener, the clear answer/steps, placeholders for personalisation, and a warm close — plus variants (resolved / need-more-info / escalating), tuned to keep it human.
npx skills add mohitagw15856/pm-claude-skills --skill support-macro --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Support Macro Skill Macros make support fast — but bad ones make it feel like a wall of copy-paste, which customers hate. A good macro is a *scaffold*: empathetic opener, the actual answer in clear steps, obvious personalisation slots, and a human close — fast for the agent, warm for the customer. This skill writes that, with the variants a single situation usually needs. ## Required Inputs Ask for these only if they aren't already provided: - **The scenario** — the common ticket this macro answers (password reset, refund request, bug report, how-to). - **The resolution** — the actual answer or steps. - **Brand voice** — formal, friendly, playful (defaults to warm-professional). - **Constraints** — anything that must be said (policy, legal, security) or links to include. ## Output Format ### Macro: [scenario] **Primary macro:** > **Opener** — acknowledge the person + their issue specifically ("Sorry the export failed — let's get that sorted."). Not "Dear valued customer." > **Answer** — the resolution in clear, numbered steps where it's a process. One idea per line. > **Personalisation slots** — clearly marked `[first name]`, `[order #]`, `[specific detail]` the agent fills. > **
- Required Inputs
- Output Format
- Macro: [scenario]
- Quality Checks
- Anti-Patterns
- Based On
What does the support-macro skill do?
Write reusable support macros / canned responses that sound human, not robotic. Use when asked to write a support macro, a canned response, a saved reply, or a template for a common customer ticket. Produces a macro — an empathetic opener, the clear answer/steps, placeholders for personalisation, and a warm close — plus variants (resolved / need-more-info / escalating), tuned to keep it human.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill support-macro --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
