Pokemon champions meta

Pokémon Champions Meta

Query the bundled Pokémon Champions metagame snapshot for rankings, common configurations, partners, format comparisons, and factual changes between snapshots. This skill answers "what is popular and how is it used?"; canonical battle facts remain the responsibility of $pokemon-champions-dex.

Workflow

1. Use the current season/rule unless the user explicitly requests a historical context.
2. Use ranking for the environment overview and detail for one Pokémon's panels.
3. Use search for reverse lookup across panel entries and compare for single-vs-double facts.
4. Use report for snapshot changes. Use export-excel only when the user requests workbooks.
5. Keep usage marginals factual: common moves/items/partners are not a guaranteed joint set.

Commands

Query cached rankings:

# Uses the current season/rule by default.
python scripts/meta_query.py ranking --format single --limit 20
python scripts/meta_query.py ranking --format double --limit 20
python scripts/meta_query.py ranking --format double --season M-4 --rule M-B --limit 20

Query Pokémon details:

python scripts/meta_query.py detail --format single --pokemon 雷丘
python scripts/meta_query.py detail --format double --pokemon garchomp

Reverse-search panel entries or compare formats:

python scripts/meta_query.py search --format double --panel moves --name 地震
python scripts/meta_query.py search --format both --panel moves --type ground --category physical --min-usage 20
python scripts/meta_query.py search --format single --panel moves --where '{"and":[{"type":"Fire"},{"or":[{"category":"Special"},{"usage":">=20"}]}]}'
python scripts/meta_query.py compare --pokemon 雷丘
python scripts/meta_query.py report --format both

Names resolve through the sibling dex in Chinese, English, or Japanese. Fuzzy corrections are always disclosed: structured detail/compare results carry resolution metadata, while search reports a correction on stderr without contaminating JSON stdout.

Use JSON for downstream processing:

python scripts/meta_query.py detail --format double --pokemon garchomp --output json

Contract And Output

Treat the executable schema as the authority for commands, flags, fields, boolean query grammar, and errors:

python scripts/meta_query.py schema

Canonical JSON is language-independent. Human-readable output language precedence is --lang, then POKEMON_CHAMPIONS_LANG, then en. Read references/api.md for detailed command usage and references/schema.md only when the bundled cache layout matters.

Excel Export

export-excel always writes three standalone single-language workbooks (zh, ja, en) to the chosen output directory, independently of --lang:

python scripts/meta_query.py export-excel --season M-4 --rule M-B

This is the only command requiring openpyxl; install requirements.txt when export is needed. All query commands use the Python standard library.

Boundaries

• The shipped snapshot is read-only and queried offline; its date and season/rule stamp define freshness.
• Do not infer legality or learnsets from usage data.
• Do not combine move, item, ability, nature, partner, or spread marginals into an asserted joint set.
• A change report records factual differences between snapshots, not an interpretation of the metagame.