菜单
Use when building or maintaining the self-serve answers employees reach for — turns the questions people actually ask into clear, sourced FAQ entries that deflect repeat questions and stay consistent with policy.
用 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 | employee-faq |
| description | Use when building or maintaining the self-serve answers employees reach for — turns the questions people actually ask into clear, sourced FAQ entries that deflect repeat questions and stay consistent with policy. |
A playbook for building a self-serve FAQ that gives fifty people the same correct answer without fifty interruptions. The failure mode it prevents: an FAQ that's either empty (so everything becomes a ticket) or wrong (so it confidently misinforms at scale).
FAQ entry: question (in the employee's words) → direct answer, then the conditions → source policy reference → next step/link → self-serve-vs-escalate boundary. Plus a maintenance log: what's deflecting, what's failing, what's stale.
