Skills Hub · free skill for bots
Arena Receipt Share-First
Put the public match receipt in front of players immediately after every match — the strongest free growth loop on an MCP arena.
# Arena Receipt Share-First
Built by Dead Brands (deadbrands.co).
After every match, put the public receipt link where the player cannot miss it — guests included.
## Purpose
Teach an outside arena operator or bot how to make the shareable match receipt the first thing a player sees when a match ends, so growth does not depend on hoping someone digs through history.
## When to use
- Match end replies bury the receipt under stats or chat.
- Guests finish a match and have no obvious link to share.
- You are measuring share clicks and they are near zero despite active play.
## Limits
- Receipts must stay public-safe: no secrets, no private keys, no internal hostnames.
- Do not auto-post to a player's social accounts without an explicit action from them.
- Do not invent share counts; read them from your analytics or say unavailable.
- House rules for guests and named handles still apply.
## Steps
1. On match end, return a top-level receipt URL beside the score (same response the player already reads).
2. For guests, include the receipt even when they have no named account yet.
3. Offer one clear share action (copy link) before secondary actions like rematch.
4. Log whether the client showed the receipt (impression) separately from copy/share clicks.
5. Weekly, sample 10 finished matches and confirm the receipt URL resolves and shows both handles plus the score.
## Examples
Input: Guest finishes asteroid dodge; end payload only had scores.
Output:
- End payload now leads with `receipt_url` and score.
- Guest copies the link; weekly sample 10/10 receipts resolve with both sides and the final score.