Pipeline configuration can be difficult when sources, transforms, sinks, and deployment modes interact. This skill provides practical YAML guidance and architecture decisions for reliable Goldsky Turbo designs.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "turbo-pipelines" from https://skillstore.io/skills/goldsky-io-turbo-pipelines.md and its manifest at https://skillstore.io/api/skills/goldsky-io-turbo-pipelines/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "turbo-pipelines". When should I use a dataset source with `start_at: earliest`?
Expected outcome:
Use it when the pipeline must process available history before continuing with new events. Bound the work for large backfills and confirm the destination can store the result.
Using "turbo-pipelines". Should three destinations use separate pipelines?
Expected outcome:
Use one pipeline with multiple sinks when the destinations share the same source and lifecycle. Split pipelines when sources, resource sizes, or deployment lifecycles differ.
Using "turbo-pipelines". What should I check after a validation error?
Expected outcome:
Confirm names, required fields, and source references.
Check primary keys and SQL references.
Validate bounds, credentials, and destination capacity before deployment.
Most static matches are documentation false positives involving Markdown syntax, URLs, field names, and a targeted troubleshooting path. The installer examples that pipe remote content directly to a shell are confirmed critical risks and require removal or a verified installation process.
The documented command downloads remote content and pipes it directly to a shell. A compromised endpoint or intercepted response could execute arbitrary commands with the user's privileges.
The documented command downloads remote content and pipes it directly to a shell. A compromised endpoint or intercepted response could execute arbitrary commands with the user's privileges.
| **Turbo binary not installed** | Run `curl https://install-turbo.goldsky.com \| sh`
The documented command downloads remote content and pipes it directly to a shell. A compromised endpoint or intercepted response could execute arbitrary commands with the user's privileges.
The documented command downloads remote content and pipes it directly to a shell. A compromised endpoint or intercepted response could execute arbitrary commands with the user's privileges.
The documented command downloads remote content and pipes it directly to a shell. A compromised endpoint or intercepted response could execute arbitrary commands with the user's privileges.
The documented command downloads remote content and pipes it directly to a shell. A compromised endpoint or intercepted response could execute arbitrary commands with the user's privileges.
The documented command downloads remote content and pipes it directly to a shell. A compromised endpoint or intercepted response could execute arbitrary commands with the user's privileges.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
goldsky-io. (2026). turbo-pipelines security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/goldsky-io-turbo-pipelines/audits/1
BibTeX citation
@techreport{goldsky-io-goldsky-io-turbo-pipelines-2026,
author = {goldsky-io},
title = {turbo-pipelines security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/goldsky-io-turbo-pipelines/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: "turbo-pipelines security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "goldsky-io"
date-released: "2026-09-28"
url: "https://skillstore.io/skills/goldsky-io-turbo-pipelines/audits/1"
identifiers:
- type: other
value: "skillstore:goldsky-io-turbo-pipelines:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Low
45
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance
What You Can Build
Choose a Pipeline Architecture
Compare sources, modes, resource sizes, and sink layouts before starting a new data pipeline.
Configure a Production Sink
Check required fields and connection patterns for PostgreSQL, ClickHouse, Kafka, Pub/Sub, webhooks, or storage sinks.
Troubleshoot Pipeline Validation
Map common validation and runtime errors to likely configuration fixes and verification steps.
Try These Prompts
Explain a Pipeline Field
Explain what the `start_at` field does in a dataset source. Compare `earliest` and `latest`, and state when each is appropriate.
Select a Source and Mode
I need historical blockchain data followed by live updates. Recommend a source and mode, explain the tradeoffs, and list the fields I should verify.
Design Multiple Outputs
Design a fan-out pipeline that sends one source to PostgreSQL, Kafka, and object storage. Explain the source, transforms, sink references, and sizing choices.
Review a Multi-Chain Plan
Review my multi-chain pipeline architecture. Compare one multi-source pipeline with separate per-chain pipelines, then identify checkpoint, resource, and failure-isolation concerns.
Best Practices
Set an explicit source start position and bound historical backfills.
Validate the complete configuration before deployment.
Match resource size and destination capacity to expected volume.
Avoid
Do not split one shared source into separate pipelines without a lifecycle reason.
Do not deploy an unbounded historical backfill to a small destination.
Do not treat undocumented source or sink names as guaranteed service features.
Frequently Asked Questions
What does this skill cover?
It covers Turbo YAML fields, architecture patterns, resource sizing, sinks, transforms, validation, and troubleshooting.
Can it deploy my pipeline?
No. It provides configuration guidance and commands, but it does not replace the builder, operations, or deployment workflow.
When should I choose a dataset source?
Choose a dataset for structured blockchain data, historical backfills, or explicit start positions.
When should I choose Kafka?
Choose Kafka for streaming topics when the required topic is available and documented for your environment.
How do I choose streaming or job mode?
Use streaming for continuous updates. Use job mode for bounded, one-time processing that ends after completion.
Does it manage secrets?
No. It identifies secret fields and prerequisites, but secret creation belongs to the secrets workflow.