Install any skill in seconds. Free to start, no credit card required.
Get Started Free →goldsky-io/turbo-architecture
Design and architect Turbo pipelines.
Passed 19 of 21 test cases with the skill, and 10 of 21 without it.
and 16 more in the full report
10 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Once the pipeline architecture, source selection, and worker sizing decisions are finalized, which downstream execution skills should be referenced to write the YAML, draft SQL transforms, and configure keys?
| Checked | Without skill | With skill |
|---|---|---|
| Directs handoff to /turbo-pipelines. | Missed | Passed |
| Directs handoff to /turbo-transforms. | Missed | Passed |
| Directs handoff to /goldsky-secrets. | Missed | Passed |
The instructions your model reads when the skill loads.
Help users make architecture decisions for Turbo pipelines — source types, data flow patterns, resource sizing, sink strategies, and multi-chain deployment.
Invoke this skill when the user:
parallelism, sink performance, or throughput/turbo-architectureAsk the user about:
Use the patterns and decision guides below to recommend a pipeline architecture. Reference the templates in templates/ as starting points:
templates/linear-pipeline.yaml — Simple decode → filter → sinktemplates/fan-out-pipeline.yaml — One source → multiple sinkstemplates/fan-in-pipeline.yaml — Multiple events → UNION ALL → sinktemplates/multi-chain-templated.yaml — Per-chain pipeline patterntest cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.