📦

datasets

Name: datasets
Author: goldsky-io

Inhaltsrevision r1 Sicher 🌐 Netzwerkzugriff⚙️ Externe Befehle

Find Goldsky Blockchain Datasets

Incorrect dataset names and chain prefixes can prevent blockchain pipelines from loading data. This skill provides Goldsky reference tables and verification guidance for selecting datasets, schemas, and available versions.

Unterstützt: Claude Codex Code(CC)

📊 69 Angemessen

Maintain this Skill? Claim it 📊 69 Angemessen

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

Review the Skillstore skill "datasets" from https://skillstore.io/skills/goldsky-io-datasets.md and its manifest at https://skillstore.io/api/skills/goldsky-io-datasets/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/goldsky-io-datasets.md Signiertes manifest GET /api/skills/goldsky-io-datasets/manifest Signiertes lockfile GET /api/skills/goldsky-io-datasets/lockfile

Testen

„datasets“ wird verwendet. Which dataset contains ERC-20 transfers on Polygon?

Erwartetes Ergebnis:

Use matic.erc20_transfers. Polygon uses the matic prefix, not polygon. Verify the available version before configuring your source.

„datasets“ wird verwendet. Do Solana transactions have from_address and to_address fields?

Erwartetes Ergebnis:

The documented solana.transactions schema uses an accounts array, not from_address or to_address. For token transfers, solana.token_transfers documents from_token_account and to_token_account.

„datasets“ wird verwendet. Which dataset provides decoded contract logs on Base?

Erwartetes Ergebnis:

There is no consumable decoded_logs source in this reference. Use base.raw_logs and decode events in a SQL transform using ABI information.

Sicherheitsaudit

Sicher

v1 • 19.10.2026 Versionsbericht öffnen

All 264 static findings are false positives: Markdown formatting, legitimate read-only discovery commands, reference URLs, punctuation escapes, and a SQL primary-key declaration. The three reviewed files contain dataset documentation, chain mappings, and trigger examples; no evidence found of prompt injection, credential theft, or exfiltration. No additional semantic security findings were identified.

Gescannte Dateien

681

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Risikofaktoren

🌐 Netzwerkzugriff (3)

data/chain-prefixes.json:2 SKILL.md:23 SKILL.md:181

⚙️ Externe Befehle (50)

Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

https://skillstore.io/skills/goldsky-io-datasets/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/goldsky-io-datasets/security.svg)](https://skillstore.io/skills/goldsky-io-datasets?utm_source=security_passport_badge)

HTML-Badge

<a href="https://skillstore.io/skills/goldsky-io-datasets?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/goldsky-io-datasets/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Einbettungskarte

<iframe src="https://skillstore.io/embed/skills/goldsky-io-datasets.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

goldsky-io. (2026). datasets security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/goldsky-io-datasets/audits/1

BibTeX-Zitat

@techreport{goldsky-io-goldsky-io-datasets-2026,
  author = {goldsky-io},
  title = {datasets security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/goldsky-io-datasets/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "datasets security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "goldsky-io"
date-released: "2026-10-19"
url: "https://skillstore.io/skills/goldsky-io-datasets/audits/1"
identifiers:
  - type: other
    value: "skillstore:goldsky-io-datasets:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

Wartbarkeit

Inhalt

Gemeinschaft

Spezifikationskonformität

Was Sie erstellen können

Select a token transfer dataset

Identify the correct Goldsky dataset and chain prefix before configuring an application that tracks token transfers.

Compare blockchain schemas

Compare documented Solana and EVM transaction fields before designing wallet activity analysis.

Investigate dataset naming errors

Check an unknown dataset name against prefix rules and confirm available versions through read-only discovery.

Diese Prompts ausprobieren

Find a chain prefix

What Goldsky prefix does [chain] use? Give one documented dataset name and explain any common naming mistake.

Select a dataset

Which Goldsky dataset should I use for [activity] on [chain]? Explain the documented fields and any chain-specific source settings.

Verify dataset metadata

Help verify [dataset_name] using read-only Goldsky discovery. Report available versions, schema, and Turbo compatibility only when supported by lookup results.

Plan event data sources

Compare Goldsky sources for [contract events] on [EVM chain] and token transfers on Solana. Identify decoding needs, schema differences, and required verification.

Bewährte Praktiken

Verify the exact dataset name, version, schema, and compatibility metadata before using a source configuration.
Use non-interactive dataset discovery in agent and CI environments, and prefer exact dataset lookups.
Confirm chain-specific fields and source settings instead of applying EVM assumptions to every blockchain.

Vermeiden

Guessing prefixes from chain names, such as using polygon instead of matic.
Treating example version numbers as current without checking available versions.
Assuming every chain supports the same datasets, transaction fields, or start settings.