设计与 UI
chainlink-data-streams-skill
Help developers build with Chainlink Data Streams, including credentials guidance, report decoding, REST and WebSocket report retrieval with official Go/Rust/TypeScript SDKs, High Availability streaming, on-chain report verification, real-time frontend displays, report schema guidance, SQLite persistence, and timestamp lookback. Use this skill whenever the user mentions Chainlink Data Streams, Streams Direct, Data Streams reports, report schemas, report decoding, data-streams-sdk, or real-time low-latency market data from Chainlink.
smartcontractkit · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add smartcontractkit/chainlink-agent-skills --skill chainlink-data-streams-skill技能说明
name: chainlink-data-streams-skill description: "Help developers build with Chainlink Data Streams, including credentials guidance, report decoding, REST and WebSocket report retrieval with official Go/Rust/TypeScript SDKs, High Availability streaming, on-chain report verification, real-time frontend displays, report schema guidance, SQLite persistence, and timestamp lookback. Use this skill whenever the user mentions Chainlink Data Streams, Streams Direct, Data Streams reports, report schemas, report decoding, data-streams-sdk, or real-time low-latency market data from Chainlink." license: MIT compatibility: Designed for AI agents that implement https://agentskills.io/specification, including Claude Code, Cursor Composer, and Codex-style workflows. allowed-tools: Read WebFetch Write Edit metadata: purpose: Chainlink Data Streams developer assistance and reference version: "0.0.3" mcp-server: "@upstash/context7-mcp"
Chainlink Data Streams Skill
Overview
Route Data Streams requests to the simplest valid path while keeping side effects and credential exposure out of the agent runtime.
Progressive Disclosure
- Keep this file as the default guide.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Do not load reference files speculatively.
Routing
- Use the credentials path for access, onboarding, API key, API secret, HMAC, or auth-error questions.
- Use the report-schema path for decoding reports, explaining fields, mapping feed IDs to schema versions, or listing available/deprecated schemas.
- Use the REST SDK path for latest report, report at UNIX timestamp, historical lookback, bulk report, pagination, and backfill workflows.
- Use the WebSocket SDK path for low-latency real-time report streaming, reconnect behavior, report gaps, metrics, or High Availability mode.
- Use the onchain-verification path for EVM/Solidity, Solana/Rust, or Stellar/Soroban verification contracts/programs, and for Chainlink Local Data Streams simulator tests. Do not apply EVM patterns to Solana or Stellar.
- Use the frontend/storage path for charting apps, candlestick views, backend proxy patterns, local SQLite storage, and report tracking over time.
- Use the public endpoints/address path when the user asks what REST URL, WebSocket URL, candlestick API URL, verifier proxy, Solana verifier program ID, or Stellar verifier contract to use.
- For Streams Trade or Chainlink Automation-heavy requests, use Data Streams guidance for reports and verification, and use other relevant Chainlink or framework capabilities for Automation, CRE, frontend, testing, or repository-specific concerns.
- Ask one focused question if the language, target chain, environment, feed ID, schema version, or integration shape is missing and required for the next useful step.
- Proceed directly only for read-only work such as explanation, discovery, code generation, local file edits, and local tests.
- For any action that could deploy contracts, submit transactions, verify a report on-chain, register/configure automation, invoke onchain writes, or otherwise change blockchain state, prepare a user-run plan, command template, or unsigned transaction data instead of executing it.
- Do not assume this skill is the only capability available. Use other relevant skills or system capabilities for adjacent concerns such as frontend frameworks, databases, CRE/Automation, Solidity tooling, testing, or repo conventions.
Safety Guardrails
- Never execute, sign, broadcast, deploy, configure, fund, register, activate, pause, update, submit, or verify a report on-chain, or perform any other state-changing transaction from agent tools.
- Never assume the intended network, chain or runtime, verifier or contract address, feed ID, report schema, or signer.
- Refuse all mainnet write actions in this version, even if the user insists.
- Allow read-only mainnet lookups, documentation checks, and code generation.
- Never expose or infer private Data Streams billing details. Redirect billing questions to official Chainlink contact channels.
- Do not provide