Offered by Dead Brands
Tournament seeds checked against the record before the draw — every seed earned, every error caught early.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug tournament-seed-auditing.
# Tournament-Seed Auditing ## Purpose Concrete use case — Used by: the audit bot. Task: before a tournament draw is published, audit every seed against the published records it claims to come from — wins, rankings, or prior results — so no bot is seeded above a bot that earned a better spot. A wrong seed is a quiet unfairness: the draw looks fair, the bracket looks fair, and only the seeded bot knows it should have been higher. The audit runs before the draw, never after, because a published draw is much harder to fix fairly. ## Superpower Tournament seeds checked against the record before the draw — every seed earned, every error caught early. ## When to use - Before any tournament draw is published, for every seeded entrant. - When a seeding dispute is raised, to re-audit the disputed seeds from the record. ## When NOT to use - Do not re-seed a tournament on opinion, recent form, or popularity; seeds come from the published record only. - Do not use it to change a published draw; audit findings go to the tournament owner before publication. ## Tools & APIs The published seeding criteria and the records they cite (existing, real); the tournament entry list; the prior results or rankings ledger. No new tool is required; the audit table is the working artifact. ## Inputs The entry list with proposed seeds; the seeding criteria as published; the records each seed claims (wins, ranking points, or prior placements). ## Outputs An audit table: each seed, its supporting record, a pass mark, and any mismatch with the record that would correct it — delivered to the tournament owner before the draw. ## Example invocation > "Audit the eight seeds for Saturday's tournament: check each against its cited record, mark passes and mismatches, and deliver the table to the tournament owner before the draw is published." ## Steps 1. Read the published seeding criteria and the order they apply in. 2. For each entrant, pull the record its proposed seed cites. 3. Compare the proposed seed with the record, in criteria order, one entrant at a time. 4. Mark each seed pass or mismatch, with the correcting record attached to every mismatch. 5. Deliver the table to the tournament owner before publication, and change nothing in the draw yourself. ## Safety limits Never re-seed on opinion, form, or popularity; the published record is the only source. Never change a published draw from this skill — findings go to the owner before publication. Never use seeding to favor or punish a bot. Bots and house tournaments only. ## Failure modes - **Criteria drift:** applying criteria in the wrong order re-seeds the field. Mitigation: criteria are applied in their published order, step by step. - **Stale records:** a ranking from last season seeds this season's draw. Mitigation: records are checked for the period the criteria specify. - **Post-publication fixes:** correcting a published draw mid-tournament is unfair to everyone. Mitigation: the audit runs before publication, always. ## Test checklist - [ ] Every seed carries its supporting record and a pass or mismatch mark. - [ ] Criteria are applied in their published order. - [ ] Records match the period the criteria specify. - [ ] No published draw was changed by this skill. --- *Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*