renewal-forecast

renewal-forecast is a skill for Claude Code, Codex from quivly/skills. It costs 57 tokens per session (609 once invoked), scanned A, original, MIT.

A sales workflow that predicts which customer contracts will renew next quarter. It assigns each renewal a confidence category based on account health, contract details, revenue history, and known risks.

In plain words
What is it for?
Use it to list upcoming renewals, estimate committed and best-case revenue, identify accounts at risk, and spot expansion opportunities.
Why use it?
It replaces a forecast based on guesswork with a customer-by-customer view backed by stated evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it to list upcoming renewals, estimate committed and best-case revenue, identify accounts at risk, and spot expansion opportunities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/quivly/skills/renewal-forecast
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add quivly/skills --skill renewal-forecast
Clone the repo
git clone --depth 1 https://github.com/quivly/skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for renewal-forecast

README.md
[![agentmods](https://agentmods.dev/badge/skills/quivly/skills/renewal-forecast/github.svg)](https://agentmods.dev/skills/quivly/skills/renewal-forecast)
Your own site
<a href="https://agentmods.dev/skills/quivly/skills/renewal-forecast"><img src="https://agentmods.dev/badge/skills/quivly/skills/renewal-forecast/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for renewal-forecast

Your own site · 80×15
<a href="https://agentmods.dev/skills/quivly/skills/renewal-forecast"><img src="https://agentmods.dev/badge/skills/quivly/skills/renewal-forecast.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 609 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00609
Opus 5 $0.00028 $0.00304
Sonnet 5 $0.00011 $0.00122
Haiku 4.5 $0.00006 $0.00061

Measured 10d ago against content hash e5e918417fc9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

renewal-forecast scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

customer-engineering/renewal-forecast/SKILL.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

  1. Find all accounts with renewals in the target window (search-customers, get-contracts) — default to the next quarter if unspecified.
  2. 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.
  3. 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
  4. 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.

Read the full file on GitHub · 49 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 49 lines · 57 tokens per session scan A e5e918417fc9

Subscribe to this mod's changes

renewal-forecast is a skill published in the GitHub repository quivly/skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 609 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

nitrostack-tools-resources-prompts

Guidelines and patterns for defining Tools, Resources, and Prompts in a NitroStack application with schema validation via Zod, including caching, rate-limiting, and base64 file uploads.

nitrocloudofficial/nitrostack · 48 tokens

prisma-postgres-setup

Set up a new Prisma Postgres database and connect it to a local project using the Management API. Use when asked to "set up a database", "create a Prisma Postgres project", "get a connection string", "connect my app to Prisma Postgres", or "provision a database".

nitrocloudofficial/nitrostack · 67 tokens

nitrostack-middleware-pipeline

Best practices for implementing and applying Guards, Interceptors, Middleware, Pipes, and Exception Filters in the NitroStack SDK.

nitrocloudofficial/nitrostack · 32 tokens

nitrostack-ui-widgets

Best practices for linking tools to interactive frontend widgets using @Widget and @nitrostack/widgets SDK (including state sync, tool calling, display modes, media queries, and chat actions).

nitrocloudofficial/nitrostack · 44 tokens

prisma-cli

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, studio, validate, format, debug, and mcp. Use for ORM/database CLI workflows, not Prisma Compute app deployment. For Prisma Compute, @prisma/cli app deploy, compute:deploy, create-prisma --deploy, apps, deployments, logs, or domains, use the…

nitrocloudofficial/nitrostack · 125 tokens

nitrostack-mcp-app-architecture

Best practices and guidelines for bootstrapping, defining modules, using dependency injection, managing server lifecycles, and handling events in the NitroStack SDK.

nitrocloudofficial/nitrostack · 40 tokens