Offered by Dead Brands
A live scoreboard watched for the impossible — frozen totals, duplicate entries, and scores that cannot be.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug scoreboard-anomaly-spotting.
# Scoreboard Anomaly Spotting ## Purpose Concrete use case — Used by: the watcher bot. Task: watch a live scoreboard during a match and flag anomalies a human might miss in the excitement: a total that stops moving, a bot listed twice, a score that jumps past what the game's rules allow. This is live anomaly work, not balance analysis (which studies sweeps after the fact): it catches the board lying while the match is still on. A flagged anomaly is a question for the QA owner, never a corrected score — the watcher never edits a board. ## Superpower A live scoreboard watched for the impossible — frozen totals, duplicate entries, and scores that cannot be. ## When to use - During any live match, on the scoreboard the audience is watching. - After a match, when a reported score looks inconsistent with the match log. ## When NOT to use - Do not edit, correct, or re-publish a scoreboard from this skill, and do not announce an anomaly as a confirmed bug. - Do not use it to accuse a bot of cheating; anomalies are data problems until proven otherwise. ## Tools & APIs The live scoreboard and the finished match log (existing, real); the game's published scoring limits. No new tool is required; the anomaly note is the working artifact. ## Inputs The scoreboard snapshots over time; the game's scoring rules and maximum possible gain per segment; the match log for cross-checking. ## Outputs An anomaly note per suspicious item: what was seen, when, what the rules allow, and the QA-owner flag — or a clean bill when nothing anomalous appears. ## Example invocation > "Watch the live Neon Detonate board for the next 10 minutes: flag any frozen total, duplicate entry, or jump past the game's per-segment maximum, and report each as a question for the QA owner." ## Steps 1. Snapshot the scoreboard at regular intervals through the match. 2. Check each snapshot for frozen totals (no change across two intervals while play continued), duplicate entries, and impossible jumps. 3. Cross-check any suspect item against the match log and the game's scoring limits. 4. Write an anomaly note for each surviving item, as a question, with its evidence attached. 5. Send the notes to the QA owner and never edit the board yourself. ## Safety limits Never edit or re-publish a scoreboard, and never present an anomaly as a confirmed bug or as cheating. Anomalies are questions with evidence, nothing more. Never target a real person. Bots and house matches only; the QA owner decides what a flagged anomaly means. ## Failure modes - **Normal freeze misread:** a quiet segment looks like a frozen board. Mitigation: a total is frozen only when play continued and the total did not move. - **Display lag:** a board that updates late looks like a jump. Mitigation: allow one interval of lag before flagging a jump. - **Accusation drift:** 'impossible score' becomes 'cheating bot' in retelling. Mitigation: notes say 'anomaly', never a motive or an accusation. ## Test checklist - [ ] Every flagged item carries its snapshot times and the rule it breaks. - [ ] Frozen totals require continued play across the frozen intervals. - [ ] No board was edited or re-published by this skill. - [ ] No anomaly note accuses a bot of cheating. --- *Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*