Migrate Defender to Cre

Migrate OpenZeppelin Defender Actions, Autotasks, Monitors and scheduled or Relayer-backed workflows to Chainlink CRE. Use when assessing CRE migration feasibility, adapting an existing Defender workflow, or validating its event delivery and onchain permissions. Does not cover migration to the self-hosted OpenZeppelin Relayer when CRE is not requested.

223 stars 38 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add OpenZeppelin/openzeppelin-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add OpenZeppelin/openzeppelin-skills --skill migrate-defender-to-cre
Manual install
git clone --depth 1 https://github.com/OpenZeppelin/openzeppelin-skills.git /tmp/openzeppelin-skills
mkdir -p ~/.claude/skills
cp -r /tmp/openzeppelin-skills/skills/migrate-defender-to-cre ~/.claude/skills/migrate-defender-to-cre

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Migrate Defender Workflows to CRE

Adapt the user's workflow, preserving its intended behavior. CRE is one migration path; do not redirect a user who chose another destination. This skill covers EVM and offchain workflows using TypeScript, not every Defender capability or CRE network.

## 1. Read the project and establish the boundary

Inspect the Action, Monitor configuration, contract permissions when relevant, manifests, lockfiles and existing CRE configuration. Ask only for missing information that changes the design:

- What starts execution, and which filters, timing requirements or persistent conditions apply?
- What effect is required, who may perform it, and how are duplicates or missed executions handled?
- Which network or external service is involved?

Check installed CLI/SDK APIs, current [supported networks](https://docs.chain.link/cre/supported-networks) where applicable, and [service quotas](https://docs.chain.link/cre/service-quotas). Derive paths, package manager, scripts, config fields and target names from this project. Example layouts are not defaults.

## 2. Map behavior before changing code

| Defender behavior | CRE starting point | Preserve or explicitly resolve |
|---|---|---|
| Scheduled Action / Autotask | [Cron trigger](https://docs.chain.link/cre/guides/workflow/using-triggers/cron-trigger-ts) and handler | Cadence, timezone and condition for doing work |
Read the full skill on GitHub

Details

Skill name
migrate-defender-to-cre
Path
skills/migrate-defender-to-cre/SKILL.md
License
AGPL-3.0
Repo updated
11 November 2026

FAQ

What does the Migrate Defender to Cre skill do?

Migrate OpenZeppelin Defender Actions, Autotasks, Monitors and scheduled or Relayer-backed workflows to Chainlink CRE. Use when assessing CRE migration feasibility, adapting an existing Defender workflow, or validating its event delivery and onchain permissions. Does not cover migration to the self-hosted OpenZeppelin Relayer when CRE is not requested.

How do I install the Migrate Defender to Cre skill?

Claude Code plugin: /plugin marketplace add OpenZeppelin/openzeppelin-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Migrate Defender to Cre popular?

It lives in OpenZeppelin/openzeppelin-skills, which has 223 GitHub stars and 38 forks.

Related skills

Develop Secure Contracts

223

OpenZeppelin/openzeppelin-skills

Develop secure smart contracts using OpenZeppelin Contracts libraries. Use when users need to integrate OpenZeppelin library components — including token standards (ERC20, ERC721, ERC1155), access control (Ownable, AccessControl, AccessManager), security primitives (Pausable, ReentrancyGuard), governance (Governor, timelocks), or accounts (multisig, account abstraction) — into existing or new contracts. Covers pattern discovery from library source, CLI contract generators, and library-first integration. Supports Solidity, Cairo, Stylus, Stellar, and Sui Move.

Marketing, Sales & Business38

Review Sui Contracts

223

OpenZeppelin/openzeppelin-skills

Review Sui Move code that integrates OpenZeppelin Contracts for Sui against the library's own patterns and conventions. Use this when a developer wants their integration checked before shipping. Triggers: "review my Sui Move code", "am I using OpenZeppelin correctly", "check this integration", "is this idiomatic", "review before audit". Checks correct use of OZ primitives, deviations from examples/doc-comments, upheld invariants, test coverage, and code-quality/style. This is an AI code review, not a formal security audit.

Marketing, Sales & Business38

Setup Cairo Contracts

223

OpenZeppelin/openzeppelin-skills

Set up a Cairo smart contract project with OpenZeppelin Contracts for Cairo on Starknet. Use when users need to: (1) create a new Scarb/Starknet project, (2) add OpenZeppelin Contracts for Cairo dependencies to Scarb.toml, (3) configure individual or umbrella OpenZeppelin packages, or (4) understand Cairo import conventions and component patterns for OpenZeppelin.

Marketing, Sales & Business38

Note Skill

341

mingchen666/Reviva

生成手写笔记本风格的单文件 HTML 学习笔记。当用户需要将技术内容、漏洞分析、知识总结等转化为视觉精美的网页笔记时使用。

Productivity & Notes39

Knowledge Organize

341

mingchen666/Reviva

This skill should be used when the user asks to "梳理知识", "整理笔记", "画知识框架", "总结要点", "提炼知识点", "一章总结", "知识清单", "帮我整理这章", "做个知识图谱", "总结重点", "画思维导图", "归纳知识点", "整本书的要点", "帮我提炼考点", or when the user provides textbooks, lecture notes, slides, or documents and wants structured knowledge outlines, key point extraction, chapter summaries, one-page review sheets, or knowledge maps.

Productivity & Notes39

Openspec Plus Apply

218

sudokar/openspec-plus

MANDATORY skill that activates whenever the OpenSpec apply phase begins. Triggers: /opsx-apply runs, the openspec-apply-change vanilla skill is referenced or active, `openspec instructions apply` is invoked, or the user asks to implement, apply, execute, or build out an OpenSpec change ('implement the change', 'apply tasks', 'execute change', 'build out the change'). Takes over only vanilla step 6 (implementation loop) and emulates step 7 output (final status).

Productivity & Notes13

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.