POAP KINGS
Sub-project · Microsite

Elixir

The AI-powered chronicler and advisor for POAP KINGS. Elixir runs 24/7 inside the clan's Discord, watching the Clash Royale API on a heartbeat, deciding what's worth saying, and remembering everything.

View on GitHub Join Discord
Claude Sonnet Claude Haiku Anthropic tool use SQLite + FTS discord.py CR API Pillow
What Elixir does

Eight things,
not one thing.

Elixir isn't a single bot — it's a constellation of channel-native subagents, each with its own context, memory, and purpose.

  1. 01

    Channel-native subagents

    Dedicated agents run in #river-race, #player-progress, #clan-events, #ask-elixir, #poapkings-com, and #leader-lounge — each with its own scope and tone.

  2. 02

    Awareness loop

    One agent turn per tick sees the full situation — signals, time, standings, memory — then chooses what to post or to stay silent. No noise, just signal.

  3. 03

    Deck review

    Grounded in your actual losses. Validates suggestions against your collection so the advice is buildable, not hypothetical. Build-from-scratch supported for war.

  4. 04

    Tournament tracking

    /elixir tournament watch follows brackets and posts LLM-written recaps with card-draft analysis. Highlights moments without spamming.

  5. 05

    Trophy Hall

    Seven award types — War Champ, Iron King, Donation Champ, Perfect Week, Rookie MVP — accrue into a durable trophy case the whole clan can browse.

  6. 06

    Card quiz

    Teaches tactical literacy: trade math, cycle cost, matchup intuition. Daily-ish, opt-in, and tracked per player so you can see who's leveling up.

  7. 07

    Omnipresent scouting

    A unified cr_api tool lets Elixir scout any clan or player by tag — useful for war prep, recruiting, and answering "who is this opponent?"

  8. 08

    Scoped memory

    Public, leadership-only, and notification memories — with weekly synthesis that retires stale entries and forms longer-arc memories.

How it works

Observe.
Situate. Reason.
Remember.

A single agent turn per tick — but with the full situation in context, so the bot can choose silence when there's nothing worth saying.

1

Observe

Hourly heartbeat pulls fresh data from the Clash Royale API and diffs against known state — member lists, war status, donations, trophies.

2

Situate

Builds one Situation payload: signals, time/phase, standings, scoped memory. The whole picture, not a slice.

3

Reason

One agent turn with tool access decides what (if anything) to post, where, and in what voice. Often, it stays silent.

4

Remember

Writes scoped memories — public, leadership, or notification-only — and can self-schedule revisits for future ticks.