skills.rest
moose-code
moose-codeCOMMUNITY
Explore all skills by this author →
𝕏@jonjonclarkGitHub

indexing-config

Configures Rocket.Chat deployments for automated, secure, and scalable messaging.

2|3|Updated Mar 4, 2026
Search Tags:#yaml#config#contracts#env-vars#hyperindex#field_selection#start_block
One-click install
npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-config-moose-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: indexing-config
Source: https://github.com/moose-code/polymarket-indexer/tree/main/.claude/skills/indexing-config
Command: npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-config-moose-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write and edit config.yaml for HyperIndex deployments, ensuring correct chain/contract structures, addresses, start_block, event selection, field_selection, custom event names, env vars, address_format, and schema/output paths with YAML validation and awareness of deprecated options.

Core Features & Use Cases

  • Structure Overview: Define chains and contracts with per-contract addresses and start_block overrides, plus supports global or per-contract config.
  • Event & Field Configuration: Specify event patterns, field_selection, and custom event names to disambiguate across contracts and events.
  • Environment & Validation: Enforce required environment variables, consistent address formats, and YAML validation to prevent misconfigurations; provide guidance on deprecated options during migrations.

Quick Start

Create a new config.yaml for a HyperIndex deployment by defining chains, contracts, addresses, and RPC settings.

Frequently Asked Questions about indexing-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a config.yaml file for a HyperIndex deployment?▼

To configure config.yaml for HyperIndex, define chain and contract structures, specify addresses and start_block values, set RPC configurations, and apply global or per-contract overrides for event selection and field_selection.

What are start_block overrides and how do they work in HyperIndex config?▼

Start_block overrides in HyperIndex config.yaml allow you to set specific block heights for individual contracts, ensuring indexing begins at the correct event origin without relying solely on global chain settings.

How do I handle custom event names and field_selection across multiple contracts in config.yaml?▼

Custom event names disambiguate events across multiple contracts in config.yaml, while field_selection can be applied globally or scoped per-contract to specify exactly which event data fields are indexed.

Why is YAML validation important for HyperIndex deployments and what deprecated options should I avoid?▼

YAML validation prevents misconfigurations by enforcing required environment variables, consistent address formats, and correct schema paths, while also providing guidance to identify and migrate away from deprecated options.

Can I use environment variables to manage RPC settings and address formats in HyperIndex?▼

Yes, HyperIndex config.yaml enforces required environment variables for RPC configuration rules and maintains consistent address formatting, ensuring sensitive endpoint data is managed securely outside the YAML structure.

Related Skills

Explore More Software Engineering Skills→
quiknode-labsquiknode-labs
16

quicknode-skill

Access Quicknode RPC endpoints, Streams, gRPC, and IPFS for blockchain data.

Official
Advanced
enviodevenviodev
43

indexing-config

Validate and guide editing of HyperIndex config.yaml files for blockchain indexers.

Official
Intermediate
jobstashjobstash

address-mapping

Normalize raw location strings into standardized address schemas with country codes.

Official
Intermediate
moose-codemoose-code
2

indexing-transactions

Acknowledge:

Community
Intermediate