メニュー
Score a customer's health, start the renewal motion, and flag churn or expansion early. Trigger when the user asks "how's this account doing", "health check", "are we at risk of churn", "is this account ready to expand", or before a renewal or QBR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Work an expansion-ready account into an angle and a clean hand to sales — the second growth motion the funnel forgets. Trigger when account-health flags an EXPANSION-SIGNAL, when a healthy account asks for more unprompted, a second team wants access, or the user says "this account is ready to grow", "expansion play", "upsell", or "land and expand".
Turn a customer's recent calls, adoption signal, and roadmap status into a QBR brief that leads with the outcome they bought. Trigger when a quarterly business review is coming up, before a renewal or value-review call, or when the user says "QBR prep", "build the QBR", "quarterly review for X", or "value review".
Turn what sales hears in the field into marketing actions. Trigger when a meeting note or call recap surfaces a recurring objection, a competitor mention, the buyer's own language, a missing proof point, or a win/loss reason — or when the user says "log this for marketing", "what should marketing know", or "field intel".
Turn what customer success hears after the sale into product and retention actions. Trigger when an onboarding note, QBR, support thread, or usage review surfaces adoption friction, a churn-risk signal, a feature request that blocks expansion, or a customer who's ready to grow — or when the user says "log this for product", "retention risk", "what's the churn signal", or "post-sale feedback".
Turn a conference, meetup, or event you attend or host into booked calls. Trigger when the user is about to attend or host an event, asks how to "work the room", or names an upcoming conference/meetup.
Turn a red/amber account into a recovery play — the real risk, the re-engagement outreach, the renewal-clock timing. Trigger when account-health flags a 🔴/🟡 account, when the user says "save this account", "they're going to churn", "the customer went quiet", "renewal at risk", or right after a RETENTION-RISK line is logged.
| name | account-health |
| description | Score a customer's health, start the renewal motion, and flag churn or expansion early. Trigger when the user asks "how's this account doing", "health check", "are we at risk of churn", "is this account ready to expand", or before a renewal or QBR. |
The right-side operating skill — the equivalent of lead-qualify for the post-sale half of the bowtie. Where lead-qualify scores a deal's fit, this scores a customer's health: is value landing, is the renewal safe, is there room to grow? It reads the account book and writes the signal back into the same loop the field uses.
From ops/customers.md (or a single account the user names) and any recent post-sale notes:
Read the adoption signal. Against the account's value hypothesis — is the customer getting what they bought this to do? Usage trend, workflows live vs. in scope, who's actually using it.
Score it green / amber / red:
Watch the renewal clock. The renewal motion starts at day 60, not day 85. If the renewal date is inside 60 days, say so and start the motion now — don't wait for the contract to surface it.
Flag churn early-warnings. Name the leading indicators, not the lagging one: usage trending down, the champion gone quiet, a single-threaded account after a reorg. These precede a lost renewal; the cancellation is just when it becomes visible. When one fires, hand the recovery to churn-save.
Spot expansion-readiness. A healthy account using the core well, or a second team asking unprompted, is an expansion signal — not a renewal risk. Work it with expansion-signal.
Write the signal to the loop and update the book. Log a tagged line in ops/feedback-log.md — the same single home marketing and product read:
RETENTION-RISK: [account] — [the adoption/churn signal] → [CS or product action]EXPANSION-SIGNAL: [account] — [the readiness signal] → hand to sales with CS contextThen update the account's stage, key signal, and next step in ops/customers.md.
Don't tag every quiet week as a risk — flag it when usage, the champion, or the value story is actually slipping. A book full of false alarms gets ignored.