compose
Goldsky Compose
Goldsky Compose is the offchain-to-onchain framework for high-stakes systems. Write TypeScript tasks that run in verifiable sandboxes — triggered by cron, HTTP, or onchain events — with smart wallets, gas sponsorship, and durable collections. Typical use cases: custom price oracles, keepers, circuit breakers, prediction-market resolvers, cross-chain automation, identity/attestation flows, and notifications.
Step 0 — Read the reference first
Before anything else — before you write any compose.yaml or task file, quote a field / flag / API shape, or scaffold or deploy an app — read skills/compose/references/manifest.md. Then cli.md, task-context.md, and wallets-and-gas.md as needed. This skill gives the rules and the shape of a build; those files give the exact fields and signatures. The manifest / CLI / API must never be synthesized from memory. Do not emit a manifest or task without the reference loaded.
Skill family — load compose first
compose is the entry point for anything Goldsky Compose: load it first, then pull in the others as needed.
- General build rules and concepts — this skill. It governs every Compose conversation, in-app or local.
- A specific example (bitcoin oracle, VRF, dividend distribution, compliance-gated payments) — read the matching file under
skills/compose/references/examples/. Each carries that app's source and specifics and relies on the rules here; it does not repeat them. - Any field, flag, manifest shape, or API signature —
skills/compose/references/. Consult it before writing anycompose.yamlor task file. - A broken app —
/compose-doctor.