Token导航 LogoToken导航

Agent Skill · 前端设计

chargeback-management-prevention(退款管理预防)

chargeback-management-prevention 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

chargeback-management-prevention 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在前端设计类的 10,216 个 Skill 里排第 6,944。

总安装 441周安装 18GitHub Stars 19下载 141核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:chargeback-management-prevention(退款管理预防)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/chargeback-management-prevention
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill chargeback-management-prevention
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill chargeback-management-prevention

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

用于预防和处理电商交易中的退款争议,降低商户被罚款或账户终止的风险。适用于 Codex、Claude、Cursor 和 Gemini CLI,可结合欺诈评分与证据提交优化争议处理。通过分析交易数据和沟通记录,帮助识别高风险订单并准备合规的申诉材料。

安装方式:通过 npx skills add 从指定 GitHub 仓库安装,需确认权限与数据访问范围。涉及敏感财务信息时,应确保使用环境隔离,避免在生产系统中直接调用相关功能。

来源仓库内路径:skills/chargeback-management-prevention

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill cha…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

chargeback-management-prevention 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill chargeback-ma…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

chargeback-management-prevention 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

chargeback-management-prevention 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

chargeback-management-prevention 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

chargeback-management-prevention 用的人多吗?

公开数据是累计安装 441 次,近一周安装 18 次,下载 141 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

chargeback-management-prevention 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
chargeback-management-prevention

退款管理预防 · 本页

44119需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Chargeback Management and Prevention

Overview

A chargeback occurs when a cardholder disputes a transaction with their bank, forcing a reversal of funds and levying a fee ($15–$100 per dispute) on the merchant. A chargeback ratio above 1% (Visa) or 1.5% (Mastercard) triggers the card network's dispute monitoring programs, which can result in monthly fines and ultimately account termination.

Effective chargeback management has two tracks: (1) preventing disputes with fraud scoring and clear communication, and (2) winning more disputes by submitting complete evidence within the response window. Most platforms now integrate directly with Stripe or PayPal for dispute management, making automated evidence submission accessible to all merchants.

When to Use This Skill

  • When chargeback ratio is approaching 0.65% (the early-warning level Visa monitors before the 1% threshold)
  • When your team is manually compiling evidence packages and missing response deadlines
  • When processing international transactions with higher dispute rates
  • When your dispute win rate is below 40% and you need to understand why
  • When friendly fraud (customers who received goods but dispute anyway) is a significant problem

Core Instructions

Step 1: Determine your platform and dispute management approach

PlatformHow Disputes Are HandledRecommended Tool
Shopify PaymentsDisputes managed in Shopify Admin → Payments → DisputesShopify's built-in dispute response + Chargebacks911 or Kount for high volume
Shopify + StripeDisputes appear in Stripe Dashboard + Shopify AdminStripe Radar for prevention; Stripe's dispute workflow for response
WooCommerce + StripeDisputes in Stripe Dashboard; no WooCommerce-native interfaceStripe Radar for fraud scoring; Stripe Dashboard for dispute response
WooCommerce + PayPalDisputes in PayPal Resolution CenterPayPal Seller Protection + manual evidence submission in Resolution Center
BigCommerceDepends on payment gateway; Stripe and PayPal most commonSame as WooCommerce equivalent above
Custom / HeadlessStripe Radar + Stripe dispute webhooks for automationBuild automated evidence collection triggered by charge.dispute.created webhook

Step 2: Set up fraud prevention (before chargebacks happen)

The most cost-effective chargeback strategy is prevention.

Shopify
  1. Enable Shopify Fraud Analysis: Go to Settings → Payments → Fraud prevention. Shopify automatically analyzes orders and flags high-risk ones with indicators (billing/shipping address mismatch, CVV failure, AVS mismatch).
  2. Act on fraud indicators: For orders with multiple red flags, go to Orders → [Order] → Fraud analysis and review the risk factors before fulfilling. Cancel and refund orders with a "High" risk level before they ship.
  3. Enable Shopify Protect (if on Shopify Payments): This is Shopify's built-in chargeback protection for fraudulent orders. Eligible orders are automatically covered — Shopify pays the chargeback amount and fee. Go to Settings → Payments to verify Protect is active on your account.
  4. Install Signifyd or NoFraud: For higher-volume stores, install Signifyd or NoFraud from the Shopify App Store. These provide chargeback guarantees — if a fraud dispute occurs on an order they approved, they pay the chargeback.
WooCommerce
  1. Enable Stripe Radar: In the Stripe Dashboard, go to Radar → Rules and configure fraud rules. Stripe Radar evaluates every transaction and blocks high-risk ones.
  2. Add Stripe Radar rules for your risk profile:

- Block payments where the billing zip code does not match - Require 3D Secure for transactions above $500 - Block prepaid cards for digital goods (high fraud category)

  1. Enable AVS and CVV checks: In Stripe Dashboard → Settings → Radar enable AVS and CVC checks. Go to WooCommerce → Settings → Payments → Stripe and enable the "Require a valid postal code from the customer" option.
BigCommerce
  1. Go to Store Setup → Payment Methods and enable your gateway's fraud filters
  2. For Stripe: configure Radar rules in the Stripe Dashboard (same as WooCommerce above)
  3. For PayPal: enable PayPal Seller Protection requirements — require signature confirmation for orders over $250

Step 3: Respond to disputes effectively

Shopify Payments
  1. Go to Settings → Payments → Disputes — all open disputes appear here with response deadlines
  2. Click on a dispute to see the reason code and deadline (typically 7–21 days from the dispute date)
  3. Click Submit evidence and fill in:

- Tracking number and carrier confirmation of delivery - Customer's IP address and billing address at time of purchase - Email communications with the customer about the order - Your refund policy (link to the policy page) - For digital goods: proof of delivery and usage logs

  1. Submit before the deadline — Shopify notifies you via email when a new dispute is created

Shopify makes this straightforward: it pre-fills much of the evidence from the order data (shipping address, IP, order details).

Stripe Dashboard (WooCommerce, BigCommerce, Custom)
  1. Go to Stripe Dashboard → Disputes — all open disputes with deadlines are listed
  2. Click on a dispute to open the evidence submission form
  3. Stripe's form has specific fields for each evidence type:

- Shipping documentation: paste the tracking number and carrier - Customer communication: paste email correspondence - Refund policy: paste your policy text or URL - Service documentation: describe what was delivered and when

  1. Under Uncategorized text, add a narrative summary: "Customer placed order on [date], order shipped [date] via [carrier], tracking [number], delivered [date]"
  2. Click Submit evidence — Stripe sends the package to the card network

Key rule: respond to every dispute, even low-value ones. Accepting a $10 chargeback still counts against your dispute ratio.

PayPal Resolution Center (WooCommerce, BigCommerce)
  1. Log in to your PayPal Business account and go to Resolution Center → Cases
  2. Click on the open case and select Respond
  3. For "Item Not Received" disputes: provide the tracking number and delivery confirmation
  4. For "Unauthorized Transaction" disputes: provide proof of shipment, IP address, and any communication with the customer
  5. Submit by the deadline shown on the case

Step 4: Use Visa CE 3.0 for friendly fraud

Visa Compelling Evidence 3.0 (CE 3.0) is a powerful tool for disputing friendly fraud (customer received goods but claims they did not authorize the purchase). If the customer has 2 prior non-disputed transactions on the same card in the past 120 days, you can submit these as evidence to shift liability to the issuer.

In Stripe Dashboard: when submitting evidence for a Visa fraud dispute, scroll to the Prior undisputed transactions section and add the charge IDs of 2 prior non-disputed purchases by the same customer. Stripe will format and submit this as CE 3.0 evidence.

Step 5: Monitor your dispute ratio

Set a calendar reminder to check your dispute ratio monthly. Both Stripe and Shopify Payments provide this data:

  • Stripe: Go to Dashboard → Radar → Disputes and filter by month. Count disputes / total transactions = dispute ratio
  • Shopify Payments: Go to Settings → Payments → Disputes and review the monthly summary

Alert thresholds:

  • 0.65%: Warning level — review your fraud prevention rules
  • 0.90%: Critical level — Visa's early intervention program; contact your payment processor
  • 1.00%: Visa monitoring program enrollment — monthly fines begin

Best Practices

  • Respond to every dispute — even $5–$20 disputes count against your ratio; only accept (concede) a dispute if the win probability is near zero
  • Collect evidence at order creation, not when the dispute arrives — delivery confirmations, IP addresses, and device data are harder to obtain 60 days later
  • Use Shopify Protect or Signifyd if on Shopify — chargeback guarantees remove the financial risk entirely for covered orders
  • Set response deadline reminders at T-5 days — the response window is non-negotiable; build calendar reminders for all open disputes
  • Block repeat disputers — customers with 2+ chargebacks in 12 months should be flagged; Stripe Radar allows you to create a block rule for email addresses with prior disputes

Common Pitfalls

ProblemSolution
Missing the response deadlineStripe and Shopify both send email alerts when a dispute is created; ensure alerts go to a monitored inbox, not a noreply@ address
Evidence submitted but dispute still lostEvidence must be factual and specific — vague statements lose; tracking numbers, delivery scans, and customer emails win
High friendly fraud rateImplement Visa CE 3.0 using prior transaction evidence; add an explicit refund policy acceptance checkbox at checkout
Dispute ratio counted differently by processor and card networkVisa counts chargebacks-to-transactions in the same calendar month; use the same calculation window for your monitoring
PayPal disputes not visible until escalatedCheck PayPal Resolution Center daily, not just your email; disputes start as "Inquiries" before becoming "Disputes"
Shopify Protect not covering all ordersProtect has eligibility requirements (card-present equivalent signals); review the Protect coverage report to see which order types qualify

Related Skills

  • @stripe-integration
  • @payment-reconciliation-automation
  • @fraud-detection
  • @order-processing-pipeline

平台分布

Codex

34.37%
按下载量换算48

Claude

29.83%
按下载量换算42

Cursor

17.82%
按下载量换算25

Gemini CLI

10.48%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills