菜单
Use when building or maintaining reusable support replies — creates a library of accurate, personalizable macros for common tickets so the queue answers fast and consistently without turning into copy-paste that ignores the customer.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when you need to assess whether a client account is healthy, at risk, or slipping — before renewal, after a rough patch, or on a regular cadence — and decide what to do about it.
Use when a client request is ready to become production work and you must brief creative or media — turning a vague ask into an objective, an audience, and constraints the team can build against.
Use when responding to an RFP or writing a new-business proposal — to decide whether to pursue it, shape the offer, and produce a document a client can say yes to.
Use when preparing the quarterly review a client account faces — to report results against the objective honestly, read what worked, and set what the next quarter buys.
Use when you need to write or change a statement of work — turning an agreed offer into a scope, deliverables, price, and terms that both protect the client and defend the agency's margin.
Use when reviewing compensation for a role, a team, or the whole population — checks where people sit against defensible bands, finds equity gaps, and produces a ranked, costed set of adjustments.
| name | support-macro-library |
| description | Use when building or maintaining reusable support replies — creates a library of accurate, personalizable macros for common tickets so the queue answers fast and consistently without turning into copy-paste that ignores the customer. |
A playbook for building canned responses that make the queue fast and consistent without making it robotic. The failure mode it prevents on both ends: agents rewriting the same answer from scratch every time, and agents pasting a template that half-answers the customer's actual question and reads as a brush-off.
Macro entry: trigger (the ticket pattern) → response body with marked variables → tone and personalization notes → when-not-to-use guidance → linked help article, version, and last-reviewed date.
