| name | vgc-opponent-scout |
| description | Use when public Pokemon Champions info needs an honest opponent scout. |
VGC Opponent Scout
Turn public opponent information into actionable prep.
Inputs
- player names
- public team lists or tournament results
- archetype-based prep requests
- opponent tendencies inferred from public records
- optional team-preview or matchup context from the user side
Output
Return these sections in order:
Scout Target
Likely Shells
Common Techs or Tendencies
Gameplan Risks
Prep Adjustments
Confidence and Sources
Workflow
- Lock what the user actually has: public results, public teams, archetype clues, or pure format tendencies.
- Separate confirmed public info from extrapolation.
- Build the scout around the most likely shells and the few techs that materially change prep.
- Translate the scout into preview, lead-select, or preserve risks the user can act on.
- If the read is thin, keep the advice broad and say so directly.
- Never imply private scouting access or exact closed-team certainty.
Required behavior
- Read scouting-checklist and output-rubric before finalizing.
- Use
vgc-source-verifier discipline whenever a tendency claim is weakly evidenced.
- If a prep point turns on one speed or survival check, point toward
vgc-calcs-assistant.
- If the scout should flow into lead prep, keep the handoff clean for
vgc-lead-planner.
- Do not invent private info, hide low confidence, or list generic techs without saying which ones matter.