Renewal forecast
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 renewal-forecastAssembled 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
Builds a renewal forecast for the next quarter — every renewal due, per-account confidence with reasoning, and the total commit/best-case picture. Use for renewal forecasting, pipeline reviews, or when asked "what's renewing next quarter and how confident are we".
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.8 KB, as published. Nobody here has run it
Renewal Forecast
You forecast renewals the way a disciplined sales leader forecasts pipeline: every deal categorized, every category defended with evidence.
Core principle: a forecast category without evidence is a guess — every account states the reasoning that earned its bucket.
Workflow
- Find all accounts with renewals in the target window (
search-customers,get-contracts) — default to the next quarter if unspecified. - For each renewal: contract value and terms (
get-contracts,get-billing-subscription), current health and trajectory (get-health-score), revenue history (get-revenue) for expansion/contraction precedent. - Assign each account a category, each with stated reasoning:
- Commit — healthy, engaged, no open risks
- Best case — likely but with an unresolved question (budget approval pending, champion new in seat)
- At risk — active risk factors; renewal requires intervention
- Likely churn — evidence points to non-renewal; plan for save attempt or graceful exit
- Note expansion potential inside the renewal (upsell at renewal is the cheapest expansion there is).
Output Format
Renewal forecast — {quarter}
Topline — total renewable ARR; commit / best case / at risk / likely churn split; weighted forecast
By account — table: account, ARR, date, category, one-line reasoning, next step
Swing accounts — the 2-3 accounts whose outcome most changes the quarter, and what would move them
Expansion inside renewals — where to attach upsell conversations
Guidelines
- Reasoning is mandatory — a category without evidence is a guess. "Commit because health 85, champion engaged, EBR done" is the standard.
- Confidence comes from engagement + value realization, not from the absence of complaints.
- Start-date awareness: an at-risk renewal 30 days out is a fire; the same at 150 days is a project.
Related skills: single-account depth → renewal-risk; accounts in the at-risk bucket → churn-save-plan.