Validate Goldsky dataset names and versions for Turbo pipelines.
npx skills add https://github.com/goldsky-io/goldsky-agent --skill datasets-goldsky-io
Please help me install this Agent Skill. Skill: datasets Source: https://github.com/goldsky-io/goldsky-agent/tree/main/skills/datasets Command: npx skills add https://github.com/goldsky-io/goldsky-agent --skill datasets-goldsky-io
Reference materials that map chain prefixes, dataset types, and versions to enable fast, correct dataset selection in Turbo pipelines and ensure consistency across environments.
Ask the skill to locate a dataset name, verify its version, and confirm chain compatibility for your Turbo pipeline.
High-intent search queries and answers about installing and using this skill.
To find the correct dataset version for Turbo pipelines, identify the target chain prefix and dataset type, then validate the selection against the available version history. This ensures the chosen dataset matches the per-chain schema for chains like Ethereum, Base, or Arbitrum.
Available Goldsky dataset types for pipeline validation include erc20_transfers, erc721_transfers, raw_transactions, logs, and blocks. These types are validated across multiple chains like Solana, Bitcoin, Stellar, Sui, NEAR, Starknet, and Fogo.
Dataset availability for erc721_transfers depends on per-chain schema compatibility across supported networks like Arbitrum and Optimism. You must verify that the selected dataset name and version align with the specific chain's available schema before pipeline execution.
To validate a dataset name, map it to the target chain and verify its version against the dataset catalog. This confirmation process ensures the selected dataset adheres to naming conventions and per-chain schemas, preventing pipeline execution errors.
Goldsky dataset selection fails version validation when the chosen dataset name does not match the available versions for the specified chain. Ensuring strict adherence to per-chain schemas and version history resolves these pipeline mapping inconsistencies.
Yes, selecting raw_transactions datasets for BSC or Avalanche requires knowledge of specific Goldsky naming conventions and available versions. Correct dataset identification ensures the data matches the per-chain schema required by Turbo pipelines.
wuyoscarCreate and validate a DeepPurpose DTI benchmark workflow with strict input validation.
herd-labsAutomate Turbo pipeline setup, validation, and deployment for blockchain data processing.
nimadorostkarImplement data validation gates for automated pipelines using Pandera or Great Expectations.
BlockRunAIQuery blockchain data across 40+ chains via standard JSON-RPC 2.0 calls.
