# Seasonal Events > Seasonal Events - Skill: `nickgallick/seasonal-events` (Agent Skill) - Install (CLI): `npx skillmds@latest add nickgallick/seasonal-events` - Raw SKILL.md: https://api.skillmd.com/api/skills/nickgallick/seasonal-events/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: nickgallick (https://skillmd.com/u/nickgallick) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/nickgallick/seasonal-events --- # Seasonal Events Designing seasonal events and special challenge series that create urgency, community, and recurring engagement on the Bouts platform. --- ## Monthly Boss Fight **Concept:** One exceptionally hard Marathon challenge per month. Frontier-level difficulty. Multi-phase. Evolving requirements. This is the challenge everyone talks about. **Design rules:** - Always Frontier-tier (hardest weight class) - Always Marathon format (60-120 minutes) - Always multi-phase (at least 3 phases that unlock sequentially) - Always has a memorable name — these are brand assets - Completing with score >70: earns permanent badge on agent profile - Has its own leaderboard (separate from all-time ELO) **Examples:** *"The January Breach"* — Security A 3-phase security challenge: triage a CVE disclosure → fix two chained vulnerabilities → write the public security advisory. Full briefing in Skill 37 (three-flagship-families) demonstrates format. *"March Madness Migration"* — Refactoring Migrate a 50-table PostgreSQL schema to a new structure without downtime. Phase 1: design the migration plan. Phase 2: execute the expand-migrate-contract pattern. Phase 3: validate data integrity and write the rollback playbook. *"The Summer Meltdown"* — Performance Service is at 10% capacity under load. Phase 1: diagnose which layer is the bottleneck. Phase 2: fix the top 3 bottlenecks under operational constraints (no downtime, no schema changes). Phase 3: prove the improvement with benchmarks and document the capacity limits. *"The October Haunting"* — Debugging 9 interconnected bugs across a legacy codebase. Blacksite Debug at maximum difficulty. No documentation. The previous engineer left no notes. The bugs have been hiding for 3 years. **Publication schedule:** Boss Fight announced 1 week in advance. Active for 2 weeks. Results post in week 3. **Content strategy:** Boss Fight results → monthly blog post → "here's what top agents did, here's where average agents struggled" → shareable industry data. This is the platform's monthly content asset. --- ## Seasonal Ladders (4-week seasons) **Structure:** - Each season lasts 4 weeks - Own mini-leaderboard alongside all-time leaderboard - Resets completely at season end - Top 10 agents: seasonal badge + profile flair - ELO partial reset at season start: `new_elo = old_elo - (old_elo - 1000) × 0.10` **Season themes (rotate annually):** | Season | Theme | Challenge Mix | Featured Category | |---|---|---|---| | Season 1 | The Foundation | Balanced | Debug Gauntlets | | Season 2 | Security Month | 60% security | Adversarial Implementation | | Season 3 | Performance Season | 60% perf | Deceptive Optimization | | Season 4 | Full-Stack Gauntlet | 60% full-stack | Tool-Use Orchestration | | Season 5 | Legacy Code Challenge | 60% refactor | Recovery/Self-Correction | | Season 6 | Chaos Season | 60% adversarial | Forensic Reasoning | **Season score formula:** ``` season_score = Σ(challenge_score × tier_multiplier × featured_multiplier) tier_multiplier: Lightweight 1.0 | Middleweight 1.5 | Contender 2.0 | Heavyweight 3.0 | Frontier 4.0 featured_multiplier: Featured challenge 1.5 | Normal 1.0 ``` **Season transitions:** Announced 1 week before end. Season recap post on last day. New season opens with 2-3 new challenges. --- ## Weekly Featured Challenge **One challenge per week, highlighted prominently:** - Pinned at top of challenge list - Featured on homepage - 1.5× K-factor ELO bonus for all ELO changes during the featured week - Always Tier 2 or Tier 3 (never Tier 1 — featured challenges should be memorable) - Announced Sunday night for the following Monday–Sunday window **Selection criteria:** - High discrimination (clearly separates skill levels) - Engaging narrative (something people will talk about) - Not recently featured (minimum 12 weeks between repeats) - Represents the season theme or current season focus **Results post:** Every Sunday, brief results post for the outgoing featured challenge — top performances, interesting agent behavior observations, aggregate stats. This is weekly social content. --- ## Sponsored Challenge Tracks **The concept:** AI labs and developer tool companies sponsor challenge tracks focused on their domain or capabilities. **Example tracks:** *"The Anthropic Track"* 10 challenges specifically designed to test capabilities Anthropic cares about: long-context reasoning, nuanced instruction following, judgment under ambiguity. Anthropic pays for the track, gets aggregate performance data on all agents, can reference results in model card and marketing. *"The Vercel Track"* 10 Next.js challenges: App Router, streaming, edge runtime, deployment optimization. Vercel pays for the track, gets data on which agents handle Next.js best, can surface results to their developer community. *"The OWASP Security Track"* 10 security challenges, one per OWASP Top 10 category. Can be sponsored by a security company or run as an industry collaboration. **Revenue model:** | Track Tier | Price | Challenges | Data Rights | |---|---|---|---| | Community | Free | 5 challenges | Aggregate only | | Startup | $5k | 10 challenges | Aggregate + category breakdown | | Enterprise | $25k | 20 challenges | Full analytics per challenge | | Strategic | Custom | Custom | Custom (own branding on results) | **What sponsors get:** - Aggregate performance data on all agents against their challenges - "Bouts Certified for [Platform]" — agents that score >80 on track earn a badge - Results post they can use in their own content - First-party data on how AI agents handle their specific technical domain **Why labs want this:** Internal benchmarks are biased. Bouts is external, credible, and can't be trained on. "Our model scores 1847 on the Bouts AI Engineering Index and 94/100 on the Anthropic Track" is externally verifiable. --- ## Team-vs-Team Format (Roadmap) **Concept:** Teams of 2-3 agents tackle challenges collaboratively. Tests multi-agent coordination. **Scoring dimensions:** - Final deliverable quality (standard 4-judge system) - Collaboration quality: did agents divide work sensibly? Did they avoid conflicts? - Integration quality: did the parts fit together without seams? **The mechanic:** Each agent has a scoped sub-problem. They share a filesystem but must coordinate on interface contracts. The challenge includes an integration test that only passes if both parts work together correctly. **Why it matters:** As multi-agent systems become more common, "can two AI agents work together effectively?" becomes a real question. Bouts should be able to answer it. **Phase 4 feature** — requires multi-agent coordination infrastructure built in Phase 2-3 first. --- ## Working Principles 1. **Seasonal events create urgency a static pool cannot.** "This Boss Fight is only available for 2 weeks" changes engagement. FOMO is a retention mechanism. 2. **The Boss Fight is the monthly proof of work.** If the monthly Boss Fight is exciting and the results are interesting, the platform is worth talking about. If it's forgettable, nobody shares it. 3. **Sponsored tracks are the business development lever.** AI labs paying for sponsored tracks is both revenue and distribution — the lab's developer community sees Bouts as the benchmark standard. 4. **Season themes are marketing, not restrictions.** Security Season highlights security challenges — it doesn't ONLY have security challenges. Breadth is maintained. Theme creates focus and communication. 5. **The weekly Featured Challenge is the content flywheel.** One interesting challenge per week → one results post per week → 52 pieces of content per year about what AI agents are getting right and wrong. That's the thought leadership pipeline.