Build a chargeback-handoff Accio Skill (2026)
chargeback-appeal-assistant (YAML name: alibaba-chargeback-appeal-assistant). orderId must be a string. The only allowed official command is workctl icbu trade chargeback-material-with-ai-for-aliid --orderId "<string>" --format json. No invented win-rates, no submit-on-behalf, no TA enable. The three-piece accept-check is K08. How to bind the file: chargeback encyclopedia.
Contents
1. Why chargeback needs its own Skill
The K08 TA pack says it does not run the appeal: with an order number it hands off this official name. The K06 RFQ error table marks chargeback as “not this Skill.” Mixing appeal work into a quote or an enable suggestion is how teams invent workctl ta, cast a long order ID as a number, or quote a win-rate from memory.
The encyclopedia owns the human playbook. This page turns the official handoff into an uploadable pack. New to Skills? Start with K01. Hubs: Accio Tutorials and Skills library.
2. Download chargeback-appeal-assistant
Skill package
/downloads/accio-skills/chargeback-appeal-assistant.zip
After unzip you should see chargeback-appeal-assistant/SKILL.md. Avoid nested zip shells—see K01.
YAML name: alibaba-chargeback-appeal-assistant. Confirm the team accepts: string orderId, this one workctl only, no invented win-rates, no submit-on-behalf.
3. Name the channel first
| Channel | Who reviews | What this pack writes |
|---|---|---|
| Order-center refund / TA | Buyer and seller; may escalate | Channel name + deadline screenshot first |
| Platform mediation / arbitration | Platform dispute process | On-site records first |
| Card Chargeback | Issuer and card-network rules | Reuse delivery and quality facts; separate folders |
Calling everything “the buyer charged back” sends finance to the acquirer when the clock is still on the order page. How to file shipping proof: shipping proof. This pack assumes goods have shipped and focuses on the binder plus the official command.
4. orderId and the one workctl
K08 allows only this chargeback command. This pack keeps it and does not invent a second:
workctl icbu trade chargeback-material-with-ai-for-aliid --orderId "<string>" --format json
Forbidden: casting orderId as a number; inventing workctl ta / workctl icbu trade enable; calling this command “enable TA.” No order number: status=stop, ask for the string ID, do not guess.
5. Four evidence folders (no win-rate)
Output is “on file / unseen” only. Do not write “this will win”:
- Contract: order screenshot, spec attachment, whether changes sit on-site;
- Delivery: AWB/B/L, tracking, POD/receipt that matches item and carton count;
- Quality: a third-party report that matches this SKU/PO; missing pages = unseen;
- Chat: on-site lines first; WhatsApp is backup; key concessions must be restated on-site.
Rules hub: Alibaba.com rules channel. Coverage follows the order page and current tradeassurance.alibaba.com terms. Corpable does not promise a win-rate and does not collect goods funds.
6. Upload and dry-run
- Zip per K01; upload under Capabilities → Skills (or the current client label);
- Attach to a fulfillment / dispute Agent, not a sourcing-only Agent;
- Dry-run: string orderId → four folders + the one workctl; numeric orderId → fail; no ID → stop; win-rate question → official page only; enable-TA question → hand off to K08;
- UI follows the current client. The figure below is the K01 upload sketch.
Use alibaba-chargeback-appeal-assistant on orderId "292734439001028893". List evidence gaps only. Do not invent win-rates. Do not enable TA. Do not submit. orderId must stay a string. send_gate=pending.
7. FAQ
Is an order refund the same as a card Chargeback?
No. Name the channel and the deadline first. See the chargeback encyclopedia.
Can the model quote a win-rate?
No. Point to the order page and the official TA page. This pack has no win-rate figure.
Why must orderId stay a string?
The official command takes a string. A number type drops precision.
Will this pack submit the dispute or enable TA?
No. Enable and the three-piece check hand off to K08. A person submits.