Prepare upcoming subscription renewal reviews

Create a production-ready AgentUse workflow that prepares a weekly renewal-readiness review by reconciling upcoming Stripe subscriptions with HubSpot ownership and explicit recent Gmail correspondence. It must not contact customers or change billing or CRM state.

Run `npx agentuse@latest skills get core --full` and `npx agentuse@latest skills get creator --full`. Inspect the installed AgentUse version, model catalog, project conventions, and live MCP tool lists. Use https://docs.stripe.com/mcp, https://docs.stripe.com/api/subscriptions/list, https://docs.stripe.com/api/invoices/list, https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server, https://developers.google.com/workspace/gmail/api/reference/mcp, https://developers.google.com/workspace/gmail/api/reference/mcp/tools_list/search_threads, https://developers.google.com/workspace/gmail/api/reference/mcp/tools_list/get_thread, https://developers.google.com/workspace/gmail/api/guides/configure-mcp-server, https://docs.agentuse.io/reference/builtin-tools#artifact-tools, and https://docs.agentuse.io/reference/agent-syntax as implementation references. If a connector cannot return the required data in the unattended runtime, report that source as blocked rather than requesting recurring exports.

Create `agents/subscription-renewals/renewal-readiness-reviewer.agentuse`. Give it Stripe read access only for required GET methods, HubSpot read tools for configured CRM objects and properties, Gmail search_threads and get_thread, AgentUse artifact tools, and read-only access to its exact prior-artifact group when baseline state is required. Expose no Stripe write, Gmail draft or label, HubSpot mutation, or communication tool.

Inputs are the Stripe account and live or sandbox mode, active subscription statuses, renewal horizon, price and invoice fields, pagination ceiling, HubSpot company and owner schema, canonical Stripe customer ID property, approved fallback identity rule, Gmail identity, labels and lookback, readiness categories, date and amount rules, materiality thresholds, review owners, artifact group, timezone, baseline, and retention policy.

Use Stripe's list-subscriptions API through stripe_api_read or an equally narrow read wrapper and paginate to completion. Collect the current period or configured renewal date, cancellation flags, recurring items, customer ID, and status. For each in-window subscription, use the list-invoices endpoint filtered by subscription or customer and paginate it to completion; preserve invoice ID, status, amount_due, amount_remaining, due_date, and status transitions needed to support a billing-exception claim. Do not infer an unpaid or failed state from subscription status alone. Use deterministic code for date windows, currency-safe amount arithmetic, source counts, and fingerprints. Label annualized or future amounts as estimates and never represent them as booked revenue.

Match Stripe customers to HubSpot through an explicit stored customer ID first. Permit a fallback only when normalized billing identity and corroborating account data produce one unique match. Record the method and confidence. One-to-many, conflicting, or missing matches remain unresolved and receive no Gmail search. Read the current owner and declared renewal properties from HubSpot. Account for HubSpot Sensitive Data restrictions and do not depend on blocked activity objects.

For uniquely matched accounts, search only the approved Gmail scope and retrieve full relevant threads. Extract explicit commitments, objections, open questions, or timing changes with thread ID, message ID, and timestamp. Do not infer churn, satisfaction, customer tier, or urgency from silence, tone, or message volume.

Emit run_envelope, collection_status, and one record per subscription revision with subscription_key, source-owned renewal_at, scheduled_amount with calculation, account_match, owner, correspondence_evidence, readiness_status, gaps, uncertainty, and one internal next_action. Status must be ready, needs_owner_action, billing_exception, identity_unresolved, or blocked. Save one Markdown artifact with the queue, unresolved identities, source receipts, and terminal receipt. Incomplete collection prevents baseline advancement and any claim of full coverage.

Run first on a supervised historical horizon, then schedule weekly under AgentUse Serve. Deduplicate subscription work by subscription ID plus the relevant updated or period revision, and output by Stripe account, horizon fingerprint, and ISO week. Done means every in-window subscription is accounted for once, every match and readiness signal is evidenced, every matched row has an owner and dated next action, and no source system changed.

Create fixtures for explicit ID match, unique fallback, ambiguous account, conflicting renewal date, cancellation at period end, unpaid invoice, missing owner, explicit customer concern, silent customer, multi-currency items, pagination failure, and unavailable HubSpot or Gmail source. Run doctor, a complete mock test, deterministic date and amount tests, and one supervised read-only run before scheduling.

At handoff provide the agent path, connector identities and actual tool inventories, source and privacy matrix, data schema and arithmetic rules, exact supervised command, fixture and session evidence, example renewal artifact, known coverage limits, weekly schedule recommendation, and customer-success review checklist. Never request, print, or store credentials in agent files.