contract-renewal-tracker
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.
npx skills add mohitagw15856/pm-claude-skills --skill contract-renewal-tracker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Contract Renewal Tracker Skill The auto-renewal ambush is a calendar failure wearing a legal costume: the contract renews on March 1, but the *decision* died on January 29 — the 30-day notice deadline nobody tracked ([vendor-breakup-email](../vendor-breakup-email/SKILL.md) learned this the hard way; this skill prevents needing that lesson). The tracker inventories every contract with the date that matters (notice deadline = renewal date − notice period − decision buffer), alerts at decision-time (not deadline-time — an alert with no time to decide is a countdown to the default), and attaches the renewal *ritual*: every renewal is a negotiation window and a [vendor-comparison-matrix](../vendor-comparison-matrix/SKILL.md)-lite moment, because the rubber-stamp renewal is where pricing quietly ratchets. ## What This Skill Produces - **The inventory** — every contract: vendor, cost, term, renewal date, notice period, **the computed act-by date**, owner - **The alert system** — calendar entries at act-by minus the decision buffer, with owners, in a shared calendar that survives personnel changes - **The renewal ritual** — the decision checklist: usage audit, market check, the renegotia
- What This Skill Produces
- Required Inputs
- Framework: The Tracker Rules
- Output Format
- The Inventory
- The Alert System
- The Renewal Ritual
- The Intake + Survival Rules
- Quality Checks
- Anti-Patterns
What does the contract-renewal-tracker skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill contract-renewal-tracker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.