What do I need to use Contract Renewal Tracker?

The contract population; The terms, from the documents; The owners; The calendar infrastructure.

Is Contract Renewal Tracker free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Contract Renewal Tracker

Q: How do I know the Contract Renewal Tracker output is good?

The skill verifies itself against its own quality checks: Every date came from the contract's actual clause, not memory; The calendar carries act-by dates with decision buffers, not renewal dates; Every contract has a named owner; The ritual's three checks run before any renewal.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

Never get auto-renewed into another year again — the contract inventory with the dates that matter (notice deadlines, not renewal dates), the calendar system with decision-time buffers, and the renewal-decision ritual that renegotiates instead of rubber-stamping. Use when asked track our contracts and renewals, we got auto-renewed again, when do we have to decide on this vendor, or set up renewal management. Produces the inventory with notice-deadline math, the alert system, the renewal-decision checklist, and the negotiation-window playbook.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The contract population — every recurring agreement: software ([subscription-audit](../subscription-audit/SKILL.md) finds the small ones), services, leases, insurance, maintenance; the inventory hunt mirrors the subscription hunt at company scale

▸The terms, from the documents — renewal dates and notice periods *from the contracts* (memory says "sometime in spring"; the contract says "60 days written notice" — the [tos-decoder](../tos-decoder/SKILL.md)-grade reading of the renewal clauses)

▸The owners — who decides each contract's fate; unowned contracts auto-renew by definition

▸The calendar infrastructure — where alerts live such that they survive the tracker's author leaving (the shared calendar, not the personal one)

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every date came from the contract's actual clause, not memory

✓The calendar carries act-by dates with decision buffers, not renewal dates

✓Every contract has a named owner

✓The ritual's three checks run before any renewal

✓The intake rule and quarterly sweep keep the inventory current

⚠️ What it refuses to do

Do not track renewal dates — the act-by date is the decision's real deadline

Do not alert without the decision context — archaeology-requiring alerts get snoozed into defaults

Do not rubber-stamp proven tools — the usage audit and the ask cost minutes and fund budgets

Do not keep the tracker personal — the ambushes cluster after the owner leaves

Do not sign anything into the void — no inventory row, no signature; the intake rule is the whole system's moat

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="contract-renewal-tracker"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Contract Renewal Tracker is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog