At risk report
Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.
npx -y skills add quivly/skills --skill at-risk-reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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".
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.5 KB, as published. Nobody here has run it
At-Risk Report
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.
Workflow
- Identify at-risk accounts (
search-customers): red/declining health, or active risk signals. Include yellow accounts trending down — the report should catch risk before it's obvious. - For each: health trajectory (
get-health-score), active risk signals (get-insights), and ARR (get-revenue). - Categorize each account's primary risk driver: product/value gap, support friction, relationship loss, commercial pressure, or competitive threat.
- Aggregate the exposure (
aggregate-metrics): total ARR at risk, count by severity, change vs. last period.
Output Format
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
Guidelines
- Sort by ARR exposure × urgency, not alphabetically.
- Every account needs a named play, even if the play is "triage scheduled Tuesday". "Monitoring" is not a play.
- Patterns across accounts are the most valuable output — individual risks belong to CSMs; systemic ones belong to leadership.
- Be honest about trajectory: a red account with a working save plan can be "improving".
Related skills: per-account depth → churn-save-plan; exec stepping into one account → escalation-brief.