community-esports-tournament-management-agent-skill: Instructions file for Claude Code

CLAUDE.md -- Skill 208: community-esports-tournament-management

Skill Identity

• Skill Name: community-esports-tournament-management
• Tagline: Community Esports Tournament Scheduling & Management -- Esports Tournament Operations & Bracket Management analysis & decision-support harness.
• Current Phase: Phase 5 -- Integration & Polish (PRODUCTION READY)
• Version: 1.0.0
• Folder: D:\972026\208-community-esports-tournament-management\

---

Problem This Skill Solves

Community esports tournament organizers face three structural gaps:

1. Data fragmentation: bracket standards, game rules, anti-cheat requirements, and scheduling best practices are scattered across Challonge, Battlefy, Liquipedia, game API docs, and academic papers.
2. Methodology gaps: most community TOs lack systematic bracket math knowledge -- format selection, seeding algorithms, tiebreaker rules, and multi-time-zone scheduling are done ad-hoc.
3. No self-improvement: static tournament guides don't update with new research on format fairness, anti-cheat methods, or community management.

This skill addresses all three by unifying real-time data aggregation, recognized bracket math and seeding methods, and a continuously-updated academic knowledge base into one evidence-backed, risk-disclosed workflow. It supports both English and Vietnamese.

---

Harness Flow Summary

/community-esports-tournament-management invoked
│
├─ Pre-Flight: Language detection (EN/VI)
│
├─ Step 1: sub-gather-requirements   → Clarify tournament parameters: game, team count, format preference, prize, time zones, broadcast, anti-cheat. Apply defaults with [ASSUMED] markers.
├─ Step 2: sub-evidence-collector   → Fetch authoritative data from Challonge, Battlefy, Liquipedia, Esports Charts, game APIs, anti-cheat docs. Tier-label all sources.
├─ Step 3: sub-core-analysis   → Select format via bracket math (match count formulas, time budget model), seed via skill/random/snake, handle BYEs, schedule across time zones, enforce anti-cheat, plan broadcast.
├─ Step 4: sub-knowledge-updater   → Query SECOND-KNOWLEDGE-BRAIN.md for academic evidence: surface citations with Tier 1-4 labels, detect gaps, queue crawl queries.
├─ Step 5: sub-advisor   → Synthesize into risk-disclosed conclusion with esports-specific risk taxonomy, best/base/worst scenarios, evidence chain, P0-P2 action plan.
│
└─ Step 6: Quality Gate Review → Verify U1-U6 + G1-G4, apply auto-fix (2 retry max), emit LIMITATION banner if degraded.