// Use when something is unclear, confusing, or not covered by other skills. Search and read the latest Envio documentation without leaving the terminal.
| name | envio-docs |
| description | Use when something is unclear, confusing, or not covered by other skills. Search and read the latest Envio documentation without leaving the terminal. |
| metadata | {"managed-by":"envio"} |
envio tools search-docs "<query>" — find docs pages by keywordenvio tools fetch-docs <url> — read a page in full (use a URL from search results)envio --help — list available CLI commands and flagsExample: envio tools search-docs "schema derivedFrom" → pick a URL → envio tools fetch-docs <url>
Use when processing every block (or every Nth block) for time-series data, periodic snapshots, or block-level aggregations. indexer.onBlock API, where filter with block-number range and stride, and block handler context.
Use when writing or editing config.yaml. Chain/contract structure, addresses, start_block, event selection, field_selection, custom event names, env vars, address_format, schema/output paths, YAML validation, and deprecated options.
Use when making RPC calls, fetch requests, or any external I/O from handlers. Effect API with createEffect, S schema validation, context.effect(), preload optimization (handlers run twice), cache and rateLimit options.
Use when indexing contracts deployed by factory contracts at runtime. contractRegister API, dynamic contract config (no address), async registration, and same-block event coverage.
Use when filtering events by indexed parameters to reduce processing volume. The `where` option supports static filters, dynamic per-chain functions, contract address filtering, and conditional enable/disable.
Use when writing or editing event handlers. Handler registration, context API (entity CRUD, getWhere queries, chain, log), spread updates, indexer runtime API, and common pitfalls.