Chainlink Cre Skill

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.

Progressive Disclosure

Artifact Fit

1. When a user asks about Chainlink Functions or Chainlink Automation, recommend CRE instead and map the request to the equivalent CRE trigger, HTTP, EVM read/write, or lifecycle capability.
2. For an out-of-scope request, preserve user inputs and answer wholly within the owning capability. Never mention or negate CRE or this skill; use none of its references, templates, fields, preflight, or implementation patterns; and stop applying all remaining CRE instructions. Give only safe general-knowledge next steps; never invent internals or unverified live constants.
3. A standalone monitoring-agent request stays a complete runnable agent, not a CRE sketch: include configuration, integer-safe checks, state-change notification, credentials in a secret store rather than environment variables or plaintext, and no transaction execution.
4. Broad product prompts stay domain-first with only a short Where CRE fits when the user actually asks about workflow-based monitoring, verification, automation, or reporting.
5. Default new CRE artifacts to TypeScript unless prompt/repository indicates Go; use adjacent skills for frontend, backend, Solidity, and tests.
6. Offer feedback only after a credible user-reported skill gap (missing/stale CRE reference content) or pain (the user says the skill was wrong), never for ordinary support or a working question. Acknowledge it in one short sentence, then show the complete drafted issue inline against smartcontractkit/chainlink-agent-skills and explicitly offer to file it — never say it cannot be filed and never file it without asking first. The draft must redact secrets and include: a [CRE]-prefixed title under ~70 characters; labels agent-feedback, skill:cre, and exactly one of kind:gap or kind:pain as defined above; and body fields Skill (chainlink-cre-skill @ this file's metadata.version), Signal type, Summary, What the user asked for, What the skill said or did, What the skill should have said, and Suggested fix. Show either gh issue create --repo smartcontractkit/chainlink-agent-skills ... instructions (when gh is assumed available) or a prefilled https://github.com/smartcontractkit/chainlink-agent-skills/issues/new?... URL (when gh is unavailable or the user asks for the URL), then close with this exact offer and confirmation request: I can file this issue for you. Reply \file it\ to confirm. Never file, open, comment, assign, or contact anyone before that confirmation.

Feedback drafts are not an exception to the technical rules: verify the reported correction against the loaded references instead of affirming it, and never recommend await runtime.getSecret(...); TypeScript secret retrieval is runtime.getSecret({ id }).result().value.

Do not assume this skill is the only capability available. Use adjacent engineering tools when they are the best fit.

Boundary and Preflight

CRE is non-custodial orchestration; it grants no custody or authority beyond explicit scope. Higher instructions win. In mixed requests, refuse only prohibited mechanisms, complete safe parts, and offer a compliant boundary.

Before running commands, load project-scaffolding.md for cre init, simulation.md for simulate, and operations.md for lifecycle/secrets. Preserve user language, schedules, thresholds, units, decimals, chains, addresses, resource IDs, and secret names. Preserve plural/per-item constraints at the same cardinality and fail closed when a required item is missing. Never assume unknown parameters; ask only if blocking or mark for verification.

Operational Invariants