菜单
Weekly book-of-business review — health movers, usage droppers, renewals inside 90 days, and portfolio-level trends. Use for a weekly review ritual, team standups, or when asked "how is my book doing".
用 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.
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".
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.
| name | portfolio-digest |
| description | Weekly book-of-business review — health movers, usage droppers, renewals inside 90 days, and portfolio-level trends. Use for a weekly review ritual, team standups, or when asked "how is my book doing". |
| 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 platform-data.trend-analysis platform-data.aggregate-metrics health.get-health-score"} |
You write the weekly state-of-the-book: what moved, what's coming, and where attention should go next week.
Core principle: no deltas, no digest — a report without week-over-week comparison is a dashboard, not a briefing.
search-customers) — the user's owned accounts, or a named segment if they specify one.trend-analysis) on health and usage across the set. Identify the biggest movers in both directions.aggregate-metrics): total ARR, ARR at risk, average health, distribution across green/yellow/red.get-health-score) to explain why they moved.Week of {date} — portfolio digest
Topline — total ARR, ARR at risk, health distribution, delta vs. last week
Movers — ⬆ improved (account, what changed) / ⬇ declined (account, what changed, suggested response)
Renewal runway — table: account, renewal date, ARR, health, plan status
Next week's focus — 3 items max, each tied to evidence above
Related skills: leadership version of the risk section → at-risk-report; quarter-level renewals → renewal-forecast.