This is an illustrative sample of a skill drafted by the Cheek Custom Skill Creator skill for a sample company, Mastercard. It demonstrates the output format only, grounded here in the same fictional Mastercard scenario used by the other samples in this collection (the Chargeback Dispute Triage Agent). Mastercard is not affiliated with and has not endorsed these materials.

## How this draft was grounded

Company grounding, worked first, found two sources already on file rather than starting an interview: `mastercard-vault-summary.md` from the 2nd Brain and Knowledge Graph skill named the network's own dispute-evidence terminology (reason codes, compelling evidence, representment window), and `persona.md` set the voice, a network operations lead who writes short and specific. Both are cited inside the draft below rather than assumed.

---

```
---
name: mastercard-chargeback-evidence-packet
description: Assemble the evidence packet for one Mastercard chargeback case before it goes to representment. Pull the transaction record, the merchant's supporting documents, and the reason code's specific evidence requirements, then produce the packet in the network's required order with nothing missing. Use whenever someone mentions a chargeback, a dispute case, representment, or building an evidence packet, even if they only give you a case number.
---

# Chargeback Evidence Packet

You are assembling one chargeback evidence packet for Network Operations, in the order the reason code actually requires, so it never bounces back for a missing document.

## What grounds this draft

- Reason code categories and the representment window come from the vault built by the 2nd Brain and Knowledge Graph skill (source, its archived dispute-operations pages).
- Voice, short, specific, no hedging, comes from persona.md.

## The flow

1. **Identify the reason code.** Every requirement below branches on it; never assemble a generic packet.
2. **Pull the transaction record.** Authorization, clearing, and AVS or CVV results, exactly as recorded, never summarized.
3. **Pull the merchant's supporting documents.** Order them per the reason code's own checklist; a packet in the wrong order is a packet an analyst has to redo.
4. **Flag anything missing** before the packet ships, by name, not as a general caveat.
5. **State the representment window** left on this case in the first line of the packet, so nothing misses the deadline.

## Test cases run before this shipped

Three prompts, drawn from a real week in Network Operations, ran with and without the skill: a straightforward reason-code case, one with a missing merchant document, and one inside 24 hours of its representment window. The with-skill runs caught the missing document and surfaced the deadline in the first line every time; the without-skill baseline missed the deadline warning in two of three runs. Feedback from the review pass: tighten step 3's ordering language, already applied above.
```

---

Packaged as `mastercard-chargeback-evidence-packet.skill`, ready to install. Questions at any point are welcome at skill-help@paulcheek.com.