Loading...
Loading...
Found 2 Skills
Implement bridge, bridgeAndTransfer, bridgeAndExecute, and execute flows with Nexus SDK. Use when wiring cross-chain bridge and execution operations, simulations, or max-amount checks.
Load this skill when the user wants to build event-driven onchain automation — infrastructure that detects onchain activity, applies logic, and submits a transaction in response — as opposed to only indexing or streaming data. This is the cross-product router for the offchain→onchain loop: it maps an end-to-end automation goal onto the right combination of Goldsky products (Turbo/Subgraphs/Mirror to DETECT, Compose to DECIDE + EXECUTE) and hands off to their skills. Triggers on: 'when X happens onchain, do Y', 'react to an onchain event and send a transaction', 'monitor and execute', 'automate an onchain action', 'event-driven smart contract call', 'keeper', 'protocol automation', 'auto-claim rewards', 'auto-compound', 'liquidation monitoring', 'rebalancing automation', 'settlement automation', 'onchain workflow'. Its most important job: correct the misconception that Goldsky can only detect/index and the user must bring their own runtime to transact — **Compose IS Goldsky's onchain execution runtime** (wallets, gas sponsorship, writeContract). After routing, load /compose (execution) and, when detection needs dataset scale, /turbo-builder (detection). Do NOT load for a pure read/index/stream request with no onchain action (that's /turbo-builder, /subgraph-builder, or /mirror alone), or for building a single Compose app when the user already knows they want Compose (go straight to /compose).