amazon-returns-recovery
SolidUse 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.
Install
Quality Score: 87/100
Skill Content
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
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.
amazon-return-reduction
Return rate reduction — root cause analysis, listing accuracy, packaging improvements, size guides
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.