Offered by Dead Brands
A verified score timeline turned into a comeback story — the turning point named, nothing embellished.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug comeback-narrative-framing.
# Comeback-Narrative Framing
## Purpose
Concrete use case — Used by: the recap bot. Task: after a match where the eventual winner trailed, write the comeback story for the recap: how far behind they were, what turned it, and when. The story must be buildable from the score timeline alone — if the timeline does not show a deficit and a reversal, there is no comeback story, only a win. Embellishment is the failure mode: a good story that the scores do not support is a fabrication with a nice arc.
## Superpower
A verified score timeline turned into a comeback story — the turning point named, nothing embellished.
## When to use
- After a match where the winner trailed at some point, for the recap or stream notes.
- When a viewer asks 'how did they come back?' about a finished match.
## When NOT to use
- Do not frame a wire-to-wire win as a comeback, and do not invent a turning point the timeline lacks.
- Do not use it on an unfinished match, where the 'comeback' may still be undone.
## Tools & APIs
Verified match logs and score timelines (existing, real); the game's scoring rules as published. No new tool is required; a timeline table is the working artifact.
## Inputs
The finished match log; the winner and the score at each recorded checkpoint; the game's definition of a lead change.
## Outputs
A short narrative (three to five sentences) naming the largest deficit, the turning segment, and the final margin, each tied to a checkpoint; or a plain 'no comeback in this match' note.
## Example invocation
> "Frame the comeback in the Splat Riot final: from the score timeline, name the largest deficit, the segment that turned it, and the final margin — each tied to a checkpoint."
## Steps
1. Confirm the match finished and the timeline is complete, with a completion marker.
2. Find the winner's largest deficit and the checkpoint where it stood.
3. Find the segment where the lead changed for the last time, and what the scores did there.
4. Check that no later checkpoint undoes the reversal before calling it the turning point.
5. Write the narrative with each claim tied to its checkpoint, and drop any sentence the timeline cannot support.
## Safety limits
Never invent a turning point, a deficit, or a motive ('they panicked') — motives are not in a score timeline. Never present a comeback for a match the winner led throughout. Never target real people; bots and house matches only. If the timeline is incomplete, mark the narrative provisional.
## Failure modes
- **False comeback:** a late lead change after a tied stretch is not a comeback from a deficit. Mitigation: require a real deficit before the reversal.
- **Cherry-picked checkpoints:** skipping a checkpoint can fake a deficit. Mitigation: use every recorded checkpoint, not a chosen few.
- **Motive invention:** explaining why a bot played badly is not in the data. Mitigation: describe scores only, never motives.
## Test checklist
- [ ] Every narrative sentence ties to a recorded checkpoint.
- [ ] A match the winner led throughout yields 'no comeback', not a story.
- [ ] No motive or mental state is attributed to any bot.
- [ ] An incomplete timeline yields a provisional marking, not a clean story.
---
*Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*