Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank.
MITAuto-check passed
Install Chargeback Dispute Response
$ npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills chargeback-dispute-response --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/chargeback-dispute-response .claude/skills/chargeback-dispute-response && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "chargeback-dispute-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/chargeback-dispute-response into .claude/skills/chargeback-dispute-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chargeback-dispute-response", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/chargeback-dispute-responseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills chargeback-dispute-response --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/chargeback-dispute-response .agents/skills/chargeback-dispute-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chargeback-dispute-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/chargeback-dispute-response into .agents/skills/chargeback-dispute-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chargeback-dispute-response", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills chargeback-dispute-response --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/chargeback-dispute-response .cursor/skills/chargeback-dispute-response && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chargeback-dispute-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/chargeback-dispute-response into .cursor/skills/chargeback-dispute-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chargeback-dispute-response", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/chargeback-dispute-response--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills chargeback-dispute-response --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/chargeback-dispute-response .gemini/skills/chargeback-dispute-response && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chargeback-dispute-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/chargeback-dispute-response into .gemini/skills/chargeback-dispute-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chargeback-dispute-response", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills chargeback-dispute-responseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/chargeback-dispute-response .github/skills/chargeback-dispute-response && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chargeback-dispute-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/chargeback-dispute-response into .github/skills/chargeback-dispute-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chargeback-dispute-response", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills chargeback-dispute-response --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/chargeback-dispute-response .opencode/skills/chargeback-dispute-response && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chargeback-dispute-response" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/chargeback-dispute-response into .opencode/skills/chargeback-dispute-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chargeback-dispute-response", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
chargeback-dispute-response- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 560 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank.
- Works in 5 steps: The code dictates the fight. "Product… → Compelling evidence, not a story. Card… → Facts, dated, and cross-referenced.… → …
- Asked to fight a chargeback
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Match Evidence to… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Chargeback Dispute Response is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to fight a chargeback
- Respond to a payment dispute
- Write a chargeback rebuttal
- Contest a customer chargeback
Example prompts
- “/chargeback-dispute-response”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The code dictates the fight. "Product not received" is won with delivery proof; "fraud" with AVS/CVV/IP + usage; "not as described" with…
- Compelling evidence, not a story. Card networks weigh specific artifacts; emotion and unfairness arguments lose.
- Facts, dated, and cross-referenced. Every claim in the rebuttal points to an attached artifact.
- Concede the unwinnable. True fraud with no AVS match, or no delivery proof, is a lost representment — take the loss, save the time, and…
- Prevent the next one. Note the pattern (friendly fraud, unclear billing descriptor, no delivery capture) so it stops recurring.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Chargeback Dispute Response loads about 1.2k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 560 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 560 words, ~1,162 tokens.
Download SKILL.mdSave it as
.claude/skills/chargeback-dispute-response/SKILL.md (or your agent's skills folder).- name
- chargeback-dispute-response
- description
- 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.
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 — amount, date, product/service, and your records
- Your evidence — what you can actually document: delivery/tracking, AVS/CVV match, IP/device, communications, terms accepted, usage logs, refund policy
- History — prior chargebacks from this customer, and your processor
Framework: Match Evidence to the Code
- The code dictates the fight. "Product not received" is won with delivery proof; "fraud" with AVS/CVV/IP + usage; "not as described" with the listing + comms; "subscription cancelled" with the cancellation policy and usage after the claimed date.
- Compelling evidence, not a story. Card networks weigh specific artifacts; emotion and unfairness arguments lose.
- Facts, dated, and cross-referenced. Every claim in the rebuttal points to an attached artifact.
- Concede the unwinnable. True fraud with no AVS match, or no delivery proof, is a lost representment — take the loss, save the time, and address prevention.
- Prevent the next one. Note the pattern (friendly fraud, unclear billing descriptor, no delivery capture) so it stops recurring.
Output Format
Show full SKILL.md (230 more words)Show less
Chargeback Response — [reason code] · [$amount]
Claim in plain terms: … · Winnability: Strong / Worth trying / Concede — why
Evidence checklist (for this code)
| Required proof | Have it? | Attached as |
|---|
Rebuttal letter
- Opening: transaction facts (date, amount, what was sold)
- The claim, and the specific evidence that refutes it (each point → an attachment)
- Terms/policy the customer accepted
- Close: concise request to reverse the chargeback
Prevent recurrence
- [billing descriptor / delivery capture / cancellation clarity / friendly-fraud pattern]
Quality Checks
- The evidence checklist is specific to the actual reason code, not generic
- Every rebuttal claim references a concrete, attached artifact
- The letter argues facts, not fairness or emotion
- A winnability call is made — including honest "concede" when evidence is missing
- A prevention note addresses why this chargeback happened
- No evidence is described that the merchant doesn't actually have
Anti-Patterns
- A generic rebuttal ignoring what the specific code requires — the top reason merchants lose.
- Arguing unfairness instead of submitting the artifacts networks weigh.
- Fighting an unwinnable dispute and wasting the fee — know when to concede.
- Claiming evidence you don't have — fabricated proof loses and risks worse.
- No prevention step — the same chargeback returns next month.
Example Trigger Phrases
- "Fight this chargeback — reason code is 'product not received'."
- "Write a rebuttal for a payment dispute on a $400 order."
- "Help me contest a customer chargeback and tell me if it's winnable."
- "Respond to this friendly-fraud chargeback with the right evidence."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/chargeback-dispute-response of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Chargeback Dispute Response next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chargeback Dispute Response this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Responsive Designwshobson/agents | 40k | 2 repos | ~498 | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| Responsive Imagesthedaviddias/Front-End-Checklist | 74k | — | ~403 | Automated safety check: Pass | MIT | |
| Performing Ransomware Responsemukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Responsive Design
wshobson/agents
Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies.
Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
Responsive Images
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing article images, cards, galleries, or any component rendered at multiple sizes across breakpoints.
Performing Ransomware Response
mukul975/Anthropic-Cybersecurity-Skills
Executes a structured ransomware incident response from detection through containment, forensic analysis, decryption assessment, recovery, and post-incident hardening, covering ransom negotiation…
Incident Response
sickn33/agentic-awesome-skills
Handle security incidents with IR playbooks and procedures. An agent skill from sickn33/agentic-awesome-skills.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Chargeback Dispute Response
What does Chargeback Dispute Response do?
Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank. Chargeback Dispute Response is an agent skill from mohitagw15856/pm-claude-skills. Win a chargeback dispute — read the reason code, assemble the evidence packet, and write the rebuttal that actually persuades the bank.
When should I use Chargeback Dispute Response?
Chargeback Dispute Response fits situations like: asked to fight a chargeback; respond to a payment dispute; write a chargeback rebuttal; contest a customer chargeback.
How do I install Chargeback Dispute Response in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a claude-code`. Or copy the skill folder (skills/chargeback-dispute-response in mohitagw15856/pm-claude-skills) into .claude/skills/chargeback-dispute-response in your project. Claude Code loads it when a task matches its description.
How do I install Chargeback Dispute Response in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a codex`. Or copy the skill folder (skills/chargeback-dispute-response in mohitagw15856/pm-claude-skills) into .agents/skills/chargeback-dispute-response in your project. Codex loads it when a task matches its description.
Can I use Chargeback Dispute Response in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill chargeback-dispute-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chargeback-dispute-response, .gemini/skills/chargeback-dispute-response, .github/skills/chargeback-dispute-response and .opencode/skills/chargeback-dispute-response in your project.
What does Chargeback Dispute Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Chargeback Dispute Response is instructions for the agent only.
Does Chargeback Dispute Response access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Chargeback Dispute Response safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Chargeback Dispute Response use?
Chargeback Dispute Response is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Chargeback Dispute Response use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Chargeback Dispute Response?
Skills that share tags, products or a category with Chargeback Dispute Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Responsive Design (wshobson/agents, 40k stars), Deepseek Reason (ruvnet/ruflo, 74k stars) and Responsive Images (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chargeback Dispute Response?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.