← ClaudeAtlas

pokemon-champions-teamlisted

Pokémon Champions single/double team building, legality validation, and team diagnostics. Use when the whole request is about producing, completing, changing, reviewing, or evaluating a Pokémon Champions team; do not trigger from isolated generic words like core/style/include. Chinese examples include "帮我组一队", "配一套双打", "带X组一队", "围绕X做一队", "这队怎么改", "这队怎么选". English examples include "build me a team", "make a doubles team", "team around X", "include X in the team", "rework this team", "review/evaluate my team". Japanese examples include "チームを組んで", "ダブルの構築を作って", "X入りで組んで", "Xを軸にした構築", "この構築を直して", "選出を見て". The mandatory UEP flow uses context-audit, intake, frame, slate-evaluate, checkpoint, and answer-audit receipt gates before presenting build results. Also use to parse or validate a team, diagnose coverage/speed/role gaps, analyze 6v6 selection, compare matchups, fine-tune SP spreads, and retrieve factual real-team evidence.
pmwl0128/pokemon_champion_agent · ★ 27 · AI & Automation · score 72
Install: claude install-skill pmwl0128/pokemon_champion_agent
# Pokémon Champions Team Build, validate, diagnose, tune, and review Pokémon Champions teams. This skill is an orchestrator: its scripts emit deterministic facts, legality verdicts, and auditable evidence; the model makes and explains strategic trade-offs. Never invent a composite team-strength score or an objective "best" team. Use the sibling skills as factual authorities: - `$pokemon-champions-dex`: names, roster, forms, types, stats, abilities, learnsets, and items. - `$pokemon-champions-meta`: current or historical usage, common configurations, and partners. - `$ncp-damage-calculator`: exact damage, KO/survival, and speed calculations. ## Mandatory Protocol Read `references/assisted_workflow.md` before every build, diagnose, evaluate, rework, or tune request. It is the authoritative reasoning and routing protocol. The non-negotiable sequence is: 1. Normalize every user-supplied name through the dex, then translate free-form intent into `team-json` and `build-context`. The scripts do not parse conversation text. 2. Run `context-audit` before building or changing a team. Resolve blocking/conflicting gaps and disclose any safe defaults. Keep its `audit_receipt`. 3. For an open-ended new build, drive `intake --next` until the guided walk reports `done:true`. Existing-team analysis does not require onboarding; ask only for blocking/conflicting gaps. 4. Ground a build in current ranking plus real joint evidence (`landscape`, `observed`, `search`, and `repset`