chargeback-dispute-response
Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank. Use when asked to fight a chargeback, respond to a payment dispute, write a chargeback rebuttal, or contest a customer chargeback. Produces the reason-code decode, the required-evidence checklist for that code, the structured rebuttal letter, and an honest read on whether this one is winnable — so you fight the right disputes and concede the rest. For merchants.
npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Chargeback Dispute Response Chargebacks are won or lost on matching the *specific reason code* to the *specific evidence* the card networks accept — not on how unfair it feels. This decodes the code, tells you exactly which proof wins that category (delivery confirmation, an AVS match, the signed terms, prior usage), assembles the rebuttal in the structure banks expect, and — importantly — tells you when a dispute is unwinnable so you don't waste the representment. > Card-network rules and win rates vary by processor and code. This structures the strongest representment; it can't guarantee the issuer's decision. ## What This Skill Produces - **The reason-code decode** — what the customer/bank is actually claiming, in plain terms - **The evidence checklist** — the specific proof that wins *this* code (not a generic pile) - **The rebuttal letter** — a structured, factual representment matched to the claim - **The winnability read** — fight, or concede and save the fee — an honest call ## Required Inputs Ask for these if not provided: - **The reason code** — the code and category (fraud, product not received, not as described, subscription/cancelled, duplicate) - **The transaction**
- What This Skill Produces
- Required Inputs
- Framework: Match Evidence to the Code
- Output Format
- Chargeback Response — [reason code] · [$amount]
- Evidence checklist (for this code)
- Rebuttal letter
- Prevent recurrence
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the chargeback-dispute-response skill do?
Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank. Use when asked to fight a chargeback, respond to a payment dispute, write a chargeback rebuttal, or contest a customer chargeback. Produces the reason-code decode, the required-evidence checklist for that code, the structured rebuttal letter, and an honest read on whether this one is winnable — so you fight the right disputes and concede the rest. For merchants.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.