chainlink-cre-skill

Create a CRE workflow by running `cre init` to scaffold the project, then define a trigger (cron, HTTP, or EVM log) with a callback handler in Go or TypeScript. Always simulate with `cre workflow simulate` before deploying.

Run `cre workflow simulate` with the appropriate `--target` flag to execute the workflow locally against test conditions. Simulation is the required default before any deployment, and mainnet deployment is refused by this skill's guardrails.

TypeScript is the default when the language is unclear, but note it runs in a QuickJS/WASM runtime, not Node.js, so Node built-ins are unavailable. Go is appropriate when your repository or prompt already indicates it.

Yes, CRE is the recommended path over Chainlink Functions or Automation. Requests for those services map to equivalent CRE triggers, HTTP capabilities, EVM read/write, or lifecycle operations.

Non-determinism comes from using system time, native randomness, or unaggregated node-mode data in DON execution. Use runtime.Now(), runtime.Rand(), and consensus aggregation for external HTTP or node-mode data.

Secrets are kept as references and accessed through runtime or Vault DON secret APIs, never hardcoded in config or code. The agent never reads credential files, keystores, or real secrets.yaml values.