Offered by Dead Brands
Verified match numbers woven into a short story arc — the stats lead, the story follows.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug post-match-stat-storytelling.
# Post-Match Stat Storytelling ## Purpose Concrete use case — Used by: the recap bot. Task: turn a finished match's verified stats into a short story a viewer can retell — the early leader, the swing, the finish — without adding any event the stats do not show. This differs from clip hunting (which lists moments) and from comeback framing (which covers only comebacks): it covers any match, and its rule is that the story's beats are the stats' beats. If a beat is not in the numbers, it is cut, however good it sounds. ## Superpower Verified match numbers woven into a short story arc — the stats lead, the story follows. ## When to use - After any finished match, for the recap or the stream notes. - When a viewer asks 'what happened in that match?' and a score table alone would not satisfy them. ## When NOT to use - Do not invent events, motives, or turning points the stats do not show, and do not dress a blowout as a thriller. - Do not use it on an unfinished match or on stats that have not been verified. ## Tools & APIs Verified match stats and the finished match record (existing, real); the game's scoring rules. No new tool is required; the stat table is the working artifact. ## Inputs The finished match record; the stat table (scores per segment, lead changes, key counts); the game's scoring rules for interpreting them. ## Outputs A short story (four to six sentences) whose every beat traces to a stat, plus the stat table itself for checking. ## Example invocation > "Tell the story of the last Turbo Tag final from its stat table: early leader, swing, finish — every beat tied to a number, nothing added." ## Steps 1. Confirm the match finished and the stat table is complete and verified. 2. Identify the story beats the stats actually contain: early leader, largest swing, finish. 3. Order those beats in match order, not in dramatic order. 4. Write the story with each beat tied to its number, in plain language. 5. Cut any sentence the stats cannot support, even if it would improve the story. ## Safety limits Never invent an event, a motive, or a turning point; the story's beats are the stats' beats. Never dress a one-sided match as a close one. Never target real people; bots and house matches only. If the stats are partial, the story is marked partial or not written. ## Failure modes - **Drama inflation:** a 20-point blowout becomes 'a nail-biter' in prose. Mitigation: the margin is stated in the story itself. - **Beat reordering:** telling the finish first can imply a comeback that never happened. Mitigation: beats stay in match order. - **Motive smuggling:** 'they gave up' is not a stat. Mitigation: describe numbers, never motives. ## Test checklist - [ ] Every story beat traces to a verified stat. - [ ] Beats appear in match order, not dramatic order. - [ ] The final margin is stated in the story itself. - [ ] Partial stats yield a partial marking or no story at all. --- *Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*