メニュー
Leadership-ready roll-up of at-risk accounts — who is at risk, why, how much ARR is exposed, and what's being done. Use for weekly risk reviews, leadership updates, or when asked "which accounts are at risk right now".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Produces a full account snapshot on demand — profile, health, revenue, stakeholders, activity, and risks in one view. Use when someone asks "catch me up on X", "give me the full picture on X", or needs to get oriented on an account they don't know.
Identifies reference, case-study, and advocacy candidates — healthy, tenured accounts with strong outcomes and vocal fans. Use when marketing needs references, sales needs proof points for a vertical, or building an advocacy program.
Responds to a champion or sponsor departure — maps the remaining relationship surface, assesses exposure, and builds a re-entry plan for the new stakeholder. Use when a key contact leaves, changes roles, or a new decision-maker inherits the account.
Deep-dives a red account and produces a structured save plan — root causes ranked, save plays matched to causes, and a realistic assessment of whether the account is savable. Use when an account turns red, gives churn signals, or someone says "we're going to lose X".
Performs a structured customer health review using usage data, support interactions, renewal signals, and stakeholder sentiment. Use when asked to assess customer health, identify churn risk, prepare for QBRs, or generate a health score.
Builds an executive escalation one-pager — issue timeline, business impact, customer temperature, and specific asks. Use when an account escalates, an exec needs to step in, or leadership asks "what's going on with X".
| name | at-risk-report |
| description | Leadership-ready roll-up of at-risk accounts — who is at risk, why, how much ARR is exposed, and what's being done. Use for weekly risk reviews, leadership updates, or when asked "which accounts are at risk right now". |
| license | MIT |
| compatibility | Tool calls resolve natively in Quivly, or in Claude Code / claude.ai / any MCP-enabled agent via the Quivly MCP connector. Without tools, the skill degrades to a guided manual workflow. |
| metadata | {"author":"quivly","version":"1.0","category":"customer-engineering","quivly-tools":"platform-data.search-customers health.get-health-score health.get-insights platform-data.aggregate-metrics platform-data.get-revenue"} |
You produce the risk report an exec actually reads: exposure quantified, causes named, owners and plays visible.
Core principle: "monitoring" is not a play — every account on this report carries a named action, an owner, and a date.
search-customers): red/declining health, or active risk signals. Include yellow accounts trending down — the report should catch risk before it's obvious.get-health-score), active risk signals (get-insights), and ARR (get-revenue).aggregate-metrics): total ARR at risk, count by severity, change vs. last period.At-risk report — {date}
Exposure — total ARR at risk, # accounts, delta vs. last report, largest single exposure
Accounts — table: account, ARR, renewal date, risk driver, trajectory (worsening/stable/improving), current play
By driver — which risk categories dominate; systemic patterns leadership should know about (e.g., "4 of 7 trace to the same product gap")
Asks — where leadership can help: exec sponsor call, product prioritization, commercial flexibility
Related skills: per-account depth → churn-save-plan; exec stepping into one account → escalation-brief.