subscription-ledger

Files (1)

• SKILL.md

SKILL.md (first lines)

# Subscription ledger

Work only from explicit owner statements in the brief. An instruction such as "add Netflix, 22.98 SGD monthly" confirms that item; a receipt, screenshot, suggested item or promotional offer alone does not. If the brief only contains extracted candidates, return needsOwner asking which to track. Invoice-backed fields follow the invoice-ledger skill.

Use subscription_list to retrieve IDs and current revisions before updating. A merchant-only match is ambiguous: ask which plan/account, never select the first. Merchant plus a plan or account label can resolve one saved item. Include inactive items before adding a previously cancelled merchant. Record cancellation only when the owner says they completed it; telling you they intend to cancel is not a cancellation. Cancelling means renewal was stopped but the owner remains paid through a stated date; cancelled means the owner says it ended. No merchant account can be changed or paid here.

subscription_record needs a fresh requestKey UUID; reuse it only for an exact retry. When a turn includes multiple original inputs, first call subscription_list(sourceInputs=true), follow nextOffset, and pass the exact sourceInputIds that support the fields. Never label unrelated later inputs as sources. If an excerpt is insufficient, ask the coordinator to read that original input with conversation_read(id). The host validates ownership and current coordinator/child run membership; a single original input is bound automatically. Updates need the baseRevision just read. Store amount as the stated decimal string, currency explicitly, and amountType fixed or variable only when known. Set cadence and status from the owner statement, and use unknown when absent. A monthly bill with a variable amount does not become a fixed recurring price. Keep nextChargeDate, trialEndDate, cancellationDeadline and paidThroughDate distinct. Resolve relative dates using Singapore time; "renews on the 5th" means the next future 5th. Never invent a cancellation deadline, charge time or tax treatment. Every supplied non-null nextChargeDate needs nextChargeEstimated explicitly: false for stated, true for inferred. Clearing the date also clears its certainty. Null explicitly clears a previously saved value. Only short merchant, plan and account labels belong here, never payment numbers, bank details or full addresses.

Inspect reminder settings with subscription_list(id). subscription_settings only changes preferences; never call it as a read. Reminders are opt-in, per item, through subscription_settings or reminderEnabled on an explicit request to remind. Enabling uses defaults of 7 days before annual renewals and cancellation deadlines, 3 before trial ends, no other renewal reminder, and 09:00 Singapore. daysBefore overrides all dates for that item; time changes the firing hour. Confirm the actual returned firesAt in Singapore time and explain estimated dates. If the notice window has passed, report the warning instead of promising a scheduled reminder. Dates and reminders commit together, edits withdraw obsolete reminders, and past delivery attempts are never automatically replayed. A pending/failed reminder is not a delivered message.

A stated future price ("Netflix goes up to 24.98 SGD on 1 December") is a pending price change: set pendingAmount, pendingCurrency and pendingEffectiveDate together, and keep amount as the current price. Never set one from a promotion, a guess or an invoice. From the effective date, reads, totals and later reminders use the new price, and the next update records it in history (the result's appliedPendingPrice says so). The effective date must be in the future; clearing all three before it drops the change, and once it is in effect, correct amount directly. Price-change notices are on unless the owner turns them off with subscription_settings(priceAlerts=false). They give a reminder 3 days before a saved price change, even when other reminders are off, and one alert when a background invoice match does not show the saved price. Report the returned firesAt and any warnings. Explain that an alert never changes the tracker.

The monthly summary is opt-in and owner-wide. subscription_summary_set(enabled, day?, time?) turns it on or off: one Telegram message on that day of each month (default the 1st, 09:00 Singapore). It is built from saved records with no model call and covers monthly equivalents, the previous calendar month's recorded changes and the next 30 days. Use subscription_summary to preview it, or to answer "what changed last month" (pass month for another month). Never call the setter as a read. The summary sees only saved records, not bank or card statements.

Give concise model-written answers. Monthly equivalents are normalized estimates, not actual spending or forecast charges; totals keep currencies separate and exclude unknown/variable/trial/cancelling prices. Surface unknowns and use subscription_list for the owner's next 30 days. The read-only Mini App has a Subscriptions tab with history and reminders. Put created/read subscription IDs in refs. There is no automatic source monitoring, external cancellation, payment, negotiation or cancellation button.

From akhilvuputuri/chief-agent, MIT.

More from akhilvuputuri/chief-agent