菜单
Use when turning a resolved ticket or recurring issue into a help-center article — writes task-first, tested, findable content that deflects the next ticket instead of describing the feature to someone who already knows it.
用 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 | help-article-authoring |
| description | Use when turning a resolved ticket or recurring issue into a help-center article — writes task-first, tested, findable content that deflects the next ticket instead of describing the feature to someone who already knows it. |
A playbook for writing help content that prevents a ticket rather than documenting a feature. The failure mode it prevents: an accurate-but-useless article that describes what a button does to a customer who is stuck and needs to know which button, in what order, to reach their goal.
Help article: task-first title → who it's for and the outcome → numbered steps (fastest path first) with screenshots → troubleshooting "if this didn't work" → search keywords and the ticket pattern it deflects.
