Chainlink Data Streams Skill

Overview

Route Data Streams requests to the simplest valid path while keeping credentials, billing information, and on-chain side effects tightly controlled.

Progressive Disclosure

1. Keep this file as the default guide.
2. Read references/credentials-and-auth.md only when the user asks how to get Data Streams credentials, how authentication works, how to configure API keys, or how to debug auth failures.
3. Read references/report-schemas.md only when the user asks about report schema versions, schema fields, deprecated or available schemas, report decoding, or how to choose the correct decoder.
4. Read references/rest-sdk.md only when the user wants Go, Rust, or TypeScript code to fetch reports through REST, including latest reports, timestamp lookups, bulk lookups, or paginated history.
5. Read references/websocket-sdk.md only when the user wants Go, Rust, or TypeScript code to stream reports through WebSockets, with or without High Availability mode.
6. Read references/onchain-verification.md only when the user wants EVM, Solana, or Stellar code that verifies Data Streams reports onchain, wants Chainlink Local mock testing for Data Streams verification, or wants review/debugging of verification code.
7. Read references/frontend-and-storage.md only when the user wants a real-time frontend, candlestick display, local SQLite persistence, or local report history tracking.
8. Read references/public-endpoints-and-addresses.md only when the user needs public REST/WebSocket/candlestick endpoint defaults, supported-network verifier proxy/program IDs, or an offline fallback for those public details.
9. Read references/official-sources.md only when the answer depends on live Data Streams facts: current endpoint behavior, feed IDs, schema availability, deprecation status, SDK package versions, verifier addresses, supported networks, or current docs.
10. Do not load reference files speculatively.