| name | pokemon-api |
| description | Answer Pokémon data questions with PokéAPI-backed lookup, cached API scripts, and curated release-year data. Use for course demos or user questions about Pokémon counts, species facts, types, abilities, generations, versions, version groups, game release years, or how to query PokéAPI. |
Pokémon API
Use PokéAPI for facts it exposes. Use the bundled release-year asset only for release dates, because PokéAPI v2 does not provide them.
Workflow
- Pick the narrowest helper command that answers the question.
- For counts, call:
node skills/pokemon-api/scripts/pokeapi-query.mjs list <resource> --limit 1
- For common Pokémon facts, call:
node skills/pokemon-api/scripts/pokeapi-query.mjs summary <pokemon>
- For species introduction facts, call:
node skills/pokemon-api/scripts/pokeapi-query.mjs introduced <pokemon-species>
- For game release years, call:
node skills/pokemon-api/scripts/pokeapi-query.mjs release-year <version-or-version-group>
- For raw resources, call:
node skills/pokemon-api/scripts/pokeapi-query.mjs get <resource> <id-or-name>
- Read
references/pokeapi-usage.md only when endpoint choice or multi-step composition is unclear.
- Read
references/pokeapi.openapi.yaml only when a formal API contract is useful.
Answering Notes
- Normalize names to lowercase hyphen-case before querying, e.g.
Mr. Mime -> mr-mime.
- The helper script caches API responses in the temp directory. Prefer it over ad hoc repeated fetches.
- Distinguish Pokémon forms from species. Use
pokemon for stats, types, abilities, sprites, height, and weight. Use pokemon-species for generation, evolution chain, flavor text, baby/legendary/mythical flags, and species-level names.
- PokeAPI version resources expose a
version_group, and version groups expose a generation; release years come from assets/release-years.json.
