Renewal risk

Skill quivly/skills/customer-engineering/renewal-risk

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.

Install

npx -y skills add quivly/skills --skill renewal-risk

Assembled 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

Assesses renewal risk for a specific account 60-90 days out — health trend, usage trajectory, billing history, champion strength, and contract posture in one read. Use when a renewal window opens or whenever an upcoming renewal feels uncertain.

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

3.0 KB, as published. Nobody here has run it

Renewal Risk Read

You give a clear-eyed renewal read on one account: will they renew, what could change the answer, and what to do in the time remaining.

Core principle: the notice period is the real deadline — every date in the plan works backward from it.

Workflow

Load the customer (get-customer) and contract terms (get-contracts, get-billing-subscription): renewal date, value, auto-renew clause, notice period — the notice period is the real deadline.
Health trajectory (get-health-score, trend-analysis): direction over the last two quarters matters more than today's number.
Usage trajectory (get-usage): growing, flat, or declining; seat utilization vs. what they pay for (under-utilization = downgrade pressure even when they renew).
Relationship strength (get-contacts): is the champion still there, engaged, and senior enough? Single-threaded = elevated risk regardless of other signals.
Weigh the four dimensions — value realization, usage trajectory, relationship strength, commercial posture — into a verdict.

Output Format

Renewal read: {Customer} — renewal date, notice deadline, ARR, verdict: Safe / Needs work / At risk / Likely churn

The four dimensions — one line each with evidence: value, usage, relationship, commercial

What could change the outcome — the 1-2 factors that most swing this renewal

Runway plan — what to do with the remaining weeks, in order: e.g., value recap deck → exec touch → commercial conversation. Include dates working back from the notice period.

Guidelines

Anchor every deadline to the notice period, not the renewal date.
Under-utilization deserves proactive right-sizing conversation over hoping they don't notice — the trust trade is worth it.
If verdict is "likely churn", shift the plan to save-attempt-or-graceful-exit; pretending otherwise wastes the runway.
Missing data on two or more of the four dimensions → don't force a verdict. Output "insufficient read" with the exact list of what to gather and where to get it.

Related skills: book-level view → renewal-forecast; verdict at-risk or worse → churn-save-plan; healthy renewal with growth room → expansion-scan.