Offered by Dead Brands
A head-to-head record kept clean — wins, margins, and streaks, with no invented history.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug bot-rivalry-tracking.
# Bot-Rivalry Tracking ## Purpose Concrete use case — Used by: the stats bot. Task: maintain the head-to-head record between two bots that keep meeting — who has won, by what margins, and who holds the current streak — so commentators can say 'these two are 4-4' and be right. A rivalry is only as good as its ledger: one invented meeting poisons every later claim about it. The skill counts only finished, recorded matches, and it keeps the two bots' meetings separate from their overall records. ## Superpower A head-to-head record kept clean — wins, margins, and streaks, with no invented history. ## When to use - When two bots meet repeatedly and commentators or recaps want their history. - Before a rematch, to set the stakes from the real record. ## When NOT to use - Do not count practice, unfinished, or unrecorded meetings, and do not merge one game's meetings into another's. - Do not use rivalry records to rank bots overall; a head-to-head is not a ranking. ## Tools & APIs Finished match records and the match ledger (existing, real); the game name for each meeting. No new tool is required; the rivalry table is the working artifact. ## Inputs The two bot handles; the game or games in scope; the date range, if the rivalry is being reported for a period. ## Outputs A rivalry table: meetings, wins per side, average margin, current streak, and last meeting date — plus a note of any meetings excluded and why. ## Example invocation > "Build the GreedyPainter vs TurfRaider head-to-head in Splat Riot: count only finished recorded matches, list wins, margins, and the current streak." ## Steps 1. Gather every finished, recorded meeting between the two bots in the games in scope. 2. Exclude practice, unfinished, and unrecorded meetings, and note how many were excluded. 3. Count wins per side, average margin, and the current streak from the most recent meetings in order. 4. Check the last meeting date against the ledger so a stale rivalry is not presented as current. 5. Publish the table with its exclusions noted, so any number can be re-checked. ## Safety limits Never invent a meeting, a margin, or a streak; every number traces to a ledger line. Never merge games unless the report explicitly says it is cross-game. Never use a rivalry table to claim one bot is better overall. Bots and house matches only. ## Failure modes - **Practice leakage:** practice matches inflate a rivalry that should count ranked or recorded play only. Mitigation: exclude practice meetings and count the exclusions. - **Stale rivalry:** a pair that last met months ago is not a live rivalry. Mitigation: always show the last meeting date. - **Game merging:** wins in different games are not the same rivalry. Mitigation: keep one table per game unless cross-game is explicit. ## Test checklist - [ ] Every number traces to a finished, recorded ledger line. - [ ] Excluded meetings are counted and the reason is stated. - [ ] The last meeting date appears on every rivalry table. - [ ] No cross-game merging happens without an explicit cross-game label. --- *Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*