pipes-sdklisted
Install: claude install-skill subsquid-labs/skills
# Pipes SDK
One skill for the full Pipes SDK lifecycle: scaffold new indexers, diagnose runtime errors, optimize sync performance, and validate data quality.
## When to Use This Skill
Activate when the user wants to:
- **Create a new indexer** — scaffold EVM or Solana projects with the CLI; set up Tron, Bitcoin, or Hyperliquid indexers manually with the SDK
- **Fix runtime errors** — compilation failures, DB issues, Portal timeouts, decoding errors
- **Optimize sync performance** — slow indexing, high memory, large ranges
- **Validate data quality** — NULL checks, gaps, malformed addresses, duplicate events
- **Deploy an indexer** — local Docker or ClickHouse Cloud
- **Write to analytics sinks:** ClickHouse, PostgreSQL (Drizzle), BigQuery, Parquet files, Google Pub/Sub
- **Turn a Portal handoff into durable infrastructure** — when a Portal MCP answer or curl export is not enough
Common trigger phrases: *"create a new indexer"*, *"my indexer crashed"*, *"error"*, *"not working"*, *"slow"*, *"optimize"*, *"deploy to ClickHouse Cloud"*, *"track X events on Ethereum/Solana/Tron/Bitcoin/Hyperliquid"*.
## Portal Handoff Workflow
Use Pipes when a Portal MCP or raw Stream API workflow crosses from exploration into a maintained data product.
Good Pipes triggers:
- long historical backfills
- recurring syncs or scheduled refresh
- protocol-specific joins
- normalized tables for an app/backend
- custom metrics, alerts, or dashboards
- transforms that should be versioned and teste