indexing-external-calls

Create typed Effect APIs for external I/O in HyperIndex handlers.

43|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/enviodev/polymarket-v2-indexer --skill indexing-external-calls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: indexing-external-calls
Source: https://github.com/enviodev/polymarket-v2-indexer/tree/main/.claude/skills/indexing-external-calls
Command: npx skills add https://github.com/enviodev/polymarket-v2-indexer --skill indexing-external-calls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of performing external I/O safely inside HyperIndex handlers by enforcing a standardized Effect API to avoid double execution, enable caching, and support rate limiting.

Core Features & Use Cases

  • Typed external calls via createEffect with input/output validation.
  • Context-aware consumption using context.effect to fetch data during handler execution.
  • Preload-safe execution with caching and rate limiting to reduce duplicate requests and improve reliability.
  • Use Case: Integrate RPC calls or HTTP requests within handlers while preserving determinism and observability.

Quick Start

Define an effect with createEffect and call it in your handler using context.effect to perform a safe external I/O.

Frequently Asked Questions about indexing-external-calls

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

FAQPage Schema
How do I make external API calls safe inside HyperIndex handlers?

To make external API calls safe within HyperIndex handlers, use a typed Effect API that enforces input/output validation via S schemas, preventing double execution and ensuring predictable data fetching.

Can I use caching and rate limiting for RPC calls in Preload-optimized handlers?

Yes, external RPC calls within Preload-optimized handlers can apply caching and rate limiting options to reduce duplicate requests, improve reliability, and maintain execution determinism.

What is the best way to validate inputs for HTTP requests in HyperIndex?

The best way to validate HTTP request inputs in HyperIndex is by defining an effect with createEffect, which uses S schemas to validate input and output data before executing external I/O.

How do I fetch data during handler execution using context.effect?

You fetch data during handler execution by defining a typed effect with createEffect and then consuming it context-aware via context.effect to perform safe, observable external I/O operations.

Why does my external I/O execute twice during HyperIndex handler execution?

External I/O executes twice when not wrapped in a standardized Effect API, which is designed to prevent double execution, enable caching, and support rate limiting for Preload-safe operations.

Does indexing-external-calls require specific dependencies to work?

No specific external dependencies are required to use indexing-external-calls, as it provides a self-contained typed Effect API for integrating HTTP requests and RPC calls within your HyperIndex handlers.