amazon-returns-recovery

Solid

Use when the user wants to audit Amazon returns or Amazon-billed subscriptions, mentions a restocking fee, short or denied refund, forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or bills them. Read order, refund, and subscription evidence first; report findings and require confirmation before chat, cancellation, or dispute. The documented cases recovered $448.31, but never promise recovery. Requires an authenticated Claude in Chrome session. NOT FOR: bank chargebacks, marketplace A-to-z seller claims, price-protection claims, or subscriptions billed outside Amazon — use subscription-recovery for those.

AI & Automation 165 stars 8 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
74
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Amazon Returns Recovery ## Why this exists This started as a test of a general-purpose contract/customer-service negotiation tool — the goal was just to see if it could hold its own in a dispute. Pointed at a live Amazon account, it surfaced two restocking fees ($44.99 and $28.50) the account owner had no idea existed, on returns processed weeks earlier. Both got waived in the same sitting — the first refunded exactly the $44.99 fee, the second came back at $30.63 (the associate rounded up past the $28.50 fee as a goodwill gesture). Total recovered from fees alone: **$75.62**, on charges the account owner never would have gone looking for. The lesson: money like this doesn't announce itself — restocking fees, partial refunds, and price-protection differences sit quietly in order history unless something goes and checks. That's what this skill automates. Treat this as a metal detector, not an autopilot: it surfaces what's buried and drafts the case, but every dispute goes through the account owner before anything gets sent. The same account also had a third case worth knowing about, even though it's outside this skill's default restocking-fee scope: a $372.69 electric shaver the account owner had already been **denied a refund on once — while still inside the return window**. Re-disputed two days after the window closed, hands-off, the case ended in a full **$372.69** refund with no return required — the associate just let the account owner keep it. Overturning an existi...

Details

Author
JasonColapietro
Repository
JasonColapietro/suede-creator-skills
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

subscription-recovery

Use when the user wants to find, audit, cancel, or dispute recurring charges billed outside Amazon, including App Store, Google Play, PayPal, direct-bill streaming, gyms, news, and SaaS. Discover charges from evidence the user directly provides or authenticated service pages, report findings first, and require confirmation before cancellation or refund contact. Never enter payment credentials or promise recovery. Requires Claude in Chrome for browser actions. NOT FOR: Amazon returns, restocking fees, or Amazon-billed Prime Video Channels, Audible, Kindle Unlimited, or Prime — use amazon-returns-recovery for those.

165 Updated today
JasonColapietro
AI & Automation Featured

amazon-return-reduction

Return rate reduction — root cause analysis, listing accuracy, packaging improvements, size guides

452 Updated 5 days ago
nexscope-ai
AI & Automation Listed

recover-from-false-positive

Recover Claude Code session logs after an Anthropic API output-classifier false positive — the "cyber-related safeguards" / "appears to violate our Usage Policy" hard failure that kills a turn mid-generation. Use to (a) surgically remove the triggering user message + error response from the active session so it resumes cleanly, (b) clean accumulated refusal turns across old sessions, and (c) stop recurrence via a per-repo CLAUDE.md framing guard. PROACTIVE: if "appears to violate our Usage Policy" or "cyber-related safeguards" appears anywhere — user message, error output, tool result, workflow failure — invoke immediately without being asked. Also trigger on: "false positive", "fake violation", "it blocked me again", "remove the refusals from the logs", "cannot resume my conversation", "scrub the session logs", or any known-legitimate repo (mining, supply-chain/sigstore, BTCPay/Lightning, chaos/infra-ops, security infra) that tripped the classifier. JSON-aware log surgeon, never a blind sed/grep delete.

0 Updated 4 days ago
88plug