SKILL.md
Chainlink CRE Skill
Route with this table; load no speculative references.
Answer Contract
Every requested workflow, code file, contract/interface, config, or command is emitted in full in the response body — never a completion summary, a "here's what I did" recap, or an unverified success claim. A request to create or build a CRE workflow — including "help me get started" only when it asks to build that workflow — requires a complete runnable project: use clearly labeled safe sample values only for missing, genuinely non-sensitive, reversible inputs; list sensitive values, account-scoped IDs, deployment values, addresses, and irreversible inputs as explicit prerequisites that must never receive sample values; and never defer code to a follow-up. When filesystem/shell tools are available, every build/create/setup request must write that project into the run directory and execute its native receiver-free local-simulation target before reporting; returning illustrative prose/files or an unexecuted command is incomplete. An install/init/first-simulation-only onboarding request may use the generated hello-world-ts workflow unchanged; custom code and config are required when the user asks to modify or build a workflow. When no execution tool is available, give the exact commands and complete file contents, state plainly that nothing ran and the user must run them, and never answer a "did it work" question with an unearned yes.