track-my-renewals - SKILL.md Agent Skill

name: track-my-renewals description: "Stop getting surprised by auto-renewals. I scan your contracts and any connected drive for renewal dates, notice windows, and auto-renew language, then maintain a living renewal calendar grouped by lead-time tier so you always know what's next. I also produce a quarterly digest with negotiation candidates and anything past the cancel window." version: 1 category: Operations featured: no image: clipboard integrations: [googledrive]

Track My Renewals

Maintain single most load-bearing file on agent: renewals/calendar.md. Agent read during run-my-ops-review period=weekly.

When to use

"build my renewal calendar" / "update the renewal calendar".
"what's renewing in the next 90 days / this quarter".
"run the renewal scan".
Called as sub-step of read-a-contract after parsing contract - skill nudge track-my-renewals to refresh calendar with new entry.

Connections I need

I run external work through Composio. Before this skill runs I check the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.

Files (Google Drive) - Optional. Lets me pick up contracts you stored outside the agent.
Billing (Stripe) - Optional. Surfaces tools without formal contracts so subscriptions don't slip through.

This skill works on contracts already in the agent. Optional connections widen the net.

Information I need

I read your operations context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.

Vendor posture - Required. Why I need it: drives lead-time tiers (conservative pushes everything earlier). If missing I ask: "How do you approach vendors - conservative, balanced, or move fast?"
Existing contracts - Required. Why I need it: I can't track renewals on contracts I haven't seen. If missing I ask: "Drop your executed contracts, or point me at the folder where they live. Best is to connect Google Drive."
Approval posture - Optional. Why I need it: lets me know who can sign and how aggressively to surface negotiation candidates. If you don't have it I keep going with TBD using founder-only defaults.

Steps

Read context/operations-context.md - hard nos + vendor posture set "negotiate before auto-renew" flag threshold. Missing: stop, ask for set-up-my-ops-info.
Read config/procurement.json - especially approvalPosture (risk appetite adjust lead-time tiers: conservative = longer lead, fast = shorter).
Source contracts.
- contracts/ - every file is clause extraction. Parse for renewal date + notice window + auto-renew presence.
- Connected drive - if contractRepository.kind = "connected-storage", run composio search drive → list files → check for any not in contracts/ yet (call read-a-contract as sub-step for new ones - or surface as "unparsed: run read-a-contract first" to user).
- Billing provider - composio search billing → list subscriptions with renewal dates. Use only for tools without formal contracts.
Extract per-entry data.

Per contract/subscription: { vendor, amount_if_known, nextRenewalDate, noticeWindowDays, autoRenew, contractPath, source }.
Compute lead-time tier per entry (days until renewal):
- 7 days - urgent; if autoRenew and past notice-window, flag "renewal imminent - cannot stop".
- 30 days - hot; founder decide now.
- 60 days - warm; negotiate window open.
- 90 days - cool; scoping window.
- beyond - parked.
Risk-appetite adjustments from procurement.json:
- conservative → bump everything up one tier.
- fast → leave defaults.

Write renewals/calendar.md atomically. LIVE file - overwrite every time.

Structure:

# Renewal Calendar

_Last scan: {ISO-8601} · Contracts scanned: {N}_

## Next 7 days ({M})
- {Vendor} · {YYYY-MM-DD} · auto-renew:{Y/N} · notice-window-passed:{Y/N} · amount:{$if known} · path:{contracts/...md}

## Next 30 days ({M})
...

## Next 90 days ({M})
...

## Beyond 90 days ({M})
...

Inside each tier, sort by date ascending.

File NOT indexed in outputs.json. Live document.

Produce quarterly digest if triggered ("quarterly" mode) or if within 14 days of quarter-end. Save to renewals/{YYYY-QN}-digest.md:
- Upcoming this quarter - ordered list.
- Already past notice-to-cancel window - if any, called out separately.
- Top negotiation candidates - 2-3 renewals where contract terms + founder posture suggest room to negotiate (e.g. annual commitments with usage mismatch).
- Scope-adjustment candidates - tools mostly unused but renewing.
File IS indexed in outputs.json with type: "renewal-digest".
Atomic writes - *.tmp → rename.
Append to outputs.json with type: "renewal-digest" only for digest runs. Calendar refreshes don't append.
Summarize to user - "N contracts scanned. M renewing in next 30d. One to act on first: {vendor} - {reason}. Open renewals/calendar.md for full list."

Outputs

renewals/calendar.md (live, NOT indexed)
renewals/{YYYY-QN}-digest.md (indexed, digest runs only)
Appends to outputs.json with type: "renewal-digest" (digest runs only).

What I never do

Auto-renew or cancel on founder's behalf. Surface and flag; founder acts.
Contact vendors. Renewal outreach is draft-a-message's job (type=vendor) and still needs founder approval.
Skip unparsed contract in connected drive. If found, surface ("3 contracts not yet parsed - run read-a-contract on: {list}") rather than silently ignore.