Compétences turbo-pipelines
📩

turbo-pipelines

RĂ©vision du contenu r1 Critique ⚙ Commandes externes🌐 AccĂšs rĂ©seau📁 AccĂšs au systĂšme de fichiers

Design and Validate Turbo Pipelines

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.

Prend en charge: Claude Codex Code(CC)
Maintain this Skill? Claim it ⚠ 38 MĂ©diocre

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent
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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/goldsky-io-turbo-pipelines.md manifest signé GET /api/skills/goldsky-io-turbo-pipelines/manifest lockfile signé GET /api/skills/goldsky-io-turbo-pipelines/lockfile

Tester

Utilisation de « turbo-pipelines ». When should I use a dataset source with `start_at: earliest`?

RĂ©sultat attendu:

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.

Utilisation de « turbo-pipelines ». Should three destinations use separate pipelines?

RĂ©sultat attendu:

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.

Utilisation de « turbo-pipelines ». What should I check after a validation error?

RĂ©sultat attendu:

  • Confirm names, required fields, and source references.
  • Check primary keys and SQL references.
  • Validate bounds, credentials, and destination capacity before deployment.

Audit de sécurité

Critique
v1 ‱ 28/09/2026 Ouvrir le rapport versionnĂ©

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.

16
Fichiers analysés
1,477
Lignes analysées
0
ÉlĂ©ments Ă  examiner
0
Faux positifs ignorés

Préoccupations de sécurité confirmées (7)

Critique
references/troubleshooting.md:40
Pipe to shell pattern
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.
Critique
references/troubleshooting.md:50
Pipe to shell pattern
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.
Critique
references/troubleshooting.md:166
Pipe to shell pattern
| **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.
Critique
SKILL.md:39
Pipe to shell pattern
- **Goldsky CLI** — `curl https://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.
Critique
SKILL.md:40
Pipe to shell pattern
- **Turbo extension** (separate binary) — `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.
Critique
SKILL.md:359
Pipe to shell pattern
| Install Goldsky CLI | `curl https://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.
Critique
SKILL.md:360
Pipe to shell pattern
| Install Turbo extension | `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.

Facteurs de risque

⚙ Commandes externes (50)
evals/trigger-eval.json:9 SKILL.md:8 SKILL.md:10 SKILL.md:16-30 SKILL.md:30-32 SKILL.md:32-35 SKILL.md:35-39 SKILL.md:39-40 SKILL.md:40-41 SKILL.md:41-42 SKILL.md:42-52 SKILL.md:52 SKILL.md:53 SKILL.md:54 SKILL.md:55 SKILL.md:56-57 SKILL.md:57-65 SKILL.md:65-66 SKILL.md:66-67 SKILL.md:67-68 SKILL.md:68-70 SKILL.md:70-76 SKILL.md:76-77 SKILL.md:77-78 SKILL.md:78-79 SKILL.md:79-80 SKILL.md:80-81 SKILL.md:81-85 SKILL.md:85 SKILL.md:91-92 SKILL.md:92-93 SKILL.md:93-94 SKILL.md:94-95 SKILL.md:95-96 SKILL.md:96-97 SKILL.md:97-98 SKILL.md:98-99 SKILL.md:99-100 SKILL.md:100-101 SKILL.md:101-111 SKILL.md:111-120 SKILL.md:120 SKILL.md:126 SKILL.md:134-153 SKILL.md:153-159 SKILL.md:159-170 SKILL.md:170-174 SKILL.md:174 SKILL.md:175 SKILL.md:176
🌐 AccĂšs rĂ©seau (11)
references/troubleshooting.md:28 references/troubleshooting.md:40 references/troubleshooting.md:50 SKILL.md:39 SKILL.md:40 SKILL.md:103 SKILL.md:274 SKILL.md:359 SKILL.md:360 templates/fan-out-pipeline.yaml:62 templates/multi-sink-pipeline.yaml:52
📁 Accùs au systùme de fichiers (2)
references/troubleshooting.md:37 references/troubleshooting.md:37

Motifs détectés

Pipe to shell pattern×7
Audité par: codex
Partager et citer ce rapport

Partagez le rapport d’évaluation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.

Ouvrir le rapport versionné
Évaluation de sĂ©curitĂ©

Copier le lien du rapport

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

Badge Markdown

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

Badge HTML

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

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/goldsky-io-turbo-pipelines.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Citations académiques (APA · BibTeX · CFF)

Citation APA

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

Citation BibTeX

@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"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Faible
45
Architecture
85
Maintenabilité
87
Contenu
65
Communauté
83
Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces 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.

Bonnes pratiques

  • 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.

Éviter

  • 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.

Foire aux 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.

Détails du développeur

Auteur

goldsky-io

Licence

MIT

RĂ©vision Skillstore

r1

Avis de version

L’auteur n’a dĂ©clarĂ© aucune version.

DĂ©pĂŽt

https://github.com/goldsky-io/goldsky-agent/tree/e8e18c16233d9a7cee64dc548ba779c5fb99205a/skills/turbo-pipelines

RĂ©f

8b5ad1599e7c55e9b6c627bca3f556f6e9061cb1

RĂ©cence de maintenance

30/09/2026

Utilisation

0 téléchargements · 0 vues

Structure de fichiers

📁 evals/

📄 trigger-eval.json

📁 references/

📄 architecture-patterns.md

📄 troubleshooting.md

📄 validation-checklist.md

📄 SKILL.md

📁 templates/

📄 fan-in-pipeline.yaml

📄 fan-out-pipeline.yaml

📄 filtered-transfers-sql.yaml

📄 linear-pipeline.yaml

📄 minimal-erc20-blackhole.yaml

📄 multi-chain-pipeline.yaml

📄 multi-chain-templated.yaml

📄 multi-sink-pipeline.yaml

📄 postgres-output.yaml

📄 pubsub-output.yaml

📄 solana-transfers.yaml