Receipt Subscription Cleaner

Identify recurring charges and subscriptions from receipts or email exports, and produce a clean summary with renewal dates, price changes, and cancellation drafts. Use when a user wants to audit spending without initiating payments or cancellations.

Security Scan

The skill's instructions, required inputs, and safeguards align with its stated purpose (audit receipts and draft cancellation messages) and it does not request unexpected credentials or install components.

Purpose & Capability

Name/description (detect recurring charges, generate summaries and drafts) match the instructions and reference docs. All described capabilities are consistent with processing user-provided receipts/exports; there are no unexplained env vars, binaries, or installs requested.

Instruction Scope

SKILL.md and references consistently limit the agent to read-only analysis of receipts and generating drafts; they explicitly forbid initiating cancellations or requesting payment credentials. The docs allow optional integrations (IMAP/email APIs, OCR, webhooks) which are reasonable for automating ingestion but should be granted only with read-only scopes and careful review because those integrations could expose mailbox data if misconfigured.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk or fetched at install time, minimizing supply-chain risk.

Credentials

The skill declares no required environment variables, credentials, or config paths. Reference docs advise using offline exports or read-only API scopes and explicitly forbid requesting or storing payment credentials, which is proportional to the stated purpose.

Persistence & Privilege

always is false and the skill does not request persistent agent-wide privileges. Autonomous invocation is allowed (platform default) but the skill's docs emphasize read-only processing and local workspace storage, so no inappropriate persistence is requested.

Assessment

This skill appears coherent and focused on analyzing receipts. Before enabling or granting access: prefer uploading offline exports (MBOX/EML/PDF/CSV) rather than giving mailbox credentials; if you do grant API/IMAP access, ensure scopes are strictly read-only and time-limited; do not provide payment or bank credentials; review any webhook endpoints you configure to ensure they point to trusted locations and that attachments are sanitized. If the publisher or source is unknown and you plan to connect live accounts, consider a short-lived, limited-permission test account first.

Receipt and Subscription Cleaner

Goal

Extract and normalize receipts to detect subscriptions, renewal cycles, and potential savings opportunities.

Best fit

• Use when the user provides email exports, receipts, or billing PDFs.
• Use when the user wants a recurring charge audit and renewal calendar.
• Use when the user wants draft cancellation emails or scripts.

Not fit

• Avoid when the user asks to cancel, refund, or dispute charges automatically.
• Avoid when the user requests access to payment methods or bank logins.
• Avoid when receipts are not available and the user cannot export data.

Quick orientation

• references/overview.md for workflow and quality bar.
• references/auth.md for access and token handling.
• references/endpoints.md for optional integrations and templates.
• references/webhooks.md for async event handling.
• references/ux.md for intake questions and output formats.
• references/troubleshooting.md for common issues.
• references/safety.md for safety and privacy guardrails.

Required inputs

• Receipt sources (email export, PDF folder, or CSV list).
• Time window and base currency.
• Known subscriptions or vendors to prioritize.
• User preferences for reminders (frequency, timezone).

Expected output

• Subscription table with vendor, amount, cycle, and next renewal estimate.
• Anomaly list (price changes, overlapping subscriptions).
• Draft cancellation email templates (not sent).
• Reminder schedule recommendations.

Operational notes

• Normalize vendor names before clustering.
• Mark confidence levels for each detected subscription.
• Keep all actions read-only; produce drafts only.

Security notes

• Do not store raw receipts outside the user workspace.
• Redact card numbers and addresses in outputs.

Safe mode

• Analyze and summarize receipts only.
• Generate draft reminders and cancellation messages without sending.

Sensitive ops

• Canceling subscriptions, disputing charges, or initiating payments is out of scope.