跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

chainlink-ccip-skill

Handle Chainlink CCIP requests including read-only route, token, message-status, and lane lookups; fee-estimation guidance; user-run cross-chain transfer and messaging artifacts; sender and receiver contract development; and CCT setup guidance. The skill never signs or broadcasts transactions. Use whenever the user mentions CCIP, Chainlink cross-chain messaging, CCIP token transfers, CCTs, or CCIP monitoring.

smartcontractkit · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add smartcontractkit/chainlink-agent-skills --skill chainlink-ccip-skill

技能说明


name: chainlink-ccip-skill description: "Handle Chainlink CCIP requests including read-only route, token, message-status, and lane lookups; fee-estimation guidance; user-run cross-chain transfer and messaging artifacts; sender and receiver contract development; and CCT setup guidance. The skill never signs or broadcasts transactions. Use whenever the user mentions CCIP, Chainlink cross-chain messaging, CCIP token transfers, CCTs, or CCIP monitoring." license: MIT compatibility: Designed for AI agents that implement https://agentskills.io/specification, including Claude Code, Cursor Composer, and Codex-style workflows. allowed-tools: Read WebFetch Write Edit metadata: version: "0.0.8"

Chainlink CCIP Skill

Overview

Route CCIP requests to the simplest valid path while keeping side effects and credential exposure out of the agent runtime.

Perform live read-only lookups and generate user-run artifacts, but never sign, broadcast, deploy, bridge, transfer, or otherwise execute an onchain write. Refuse every mainnet write workflow, including user-run write artifacts.

Progressive Disclosure

  1. Keep this file as the default guide.
  2. Read references/examples.md only when you need a concrete reference for what a good response looks like (preflight summaries, monitoring explanations, contract-generation structure).
  3. Read references/official-sources.md only when the answer depends on live CCIP facts, current tool behavior, route or token availability, or message-status surfaces.
  4. Read references/ccip-api.md whenever the answer depends on live CCIP data: message status, lane inventory, lane latency, chain or contract configuration, verifiers, or intent status.
  5. Read references/ccip-tools.md only when the user wants a tool-first workflow through CCIP CLI, API, or SDK.
  6. Read references/ccip-contracts.md only when the user wants sender or receiver contracts, token-transfer contracts, programmable token-transfer contracts, or contract setup help.
  7. Read references/ccip-cct.md only when the user wants to create a token, register it as a CCT, configure pools, set rate limits, or add networks for CCT operation.
  8. Read references/chainlink-local.md only when the user wants local simulation, local tests, or forked-environment testing for CCIP contracts.
  9. Read references/ccip-monitoring.md only when the user wants message lookup, monitoring, status explanation, lane performance, or failed-message diagnosis.
  10. Read references/ccip-discovery.md only when the user wants route connectivity checks, network classification, or supported-token discovery.
  11. Read references/ccip-solidity-examples.md only when generating or reviewing CCIP Solidity contracts and you need concrete code patterns (sender, receiver, token transfer, defensive receiver).
  12. Read references/ccip-sdk-examples.md only when the user wants TypeScript SDK usage examples for fee estimation, token transfers, messaging, or status checks.
  13. Read references/ccip-non-evm.md only when the user wants to work with CCIP on Solana, Aptos, Sui, TON, Canton, or any non-EVM chain family.
  14. Do not load reference files speculatively.

Routing

  1. Use a tool-first path for preparing sends without custom contracts, bridging artifacts, status lookup, connectivity checks, and route or token discovery.
  2. Use the CCIP API directly for every live read: message status, message search, lane existence, lane latency, chain and contract configuration. It needs no RPC endpoint, no wallet, and no local tooling. See references/ccip-api.md.
  3. Use a contract-first path for sender and receiver contract work and CCT setup flows.
  4. For non-EVM chain requests (Solana, Aptos, Sui, TON, Canton), route to the non-EVM reference for workflow guidance. Do not apply EVM-specific patterns (Solidity, Foundry, Hardhat, Chainlink Local) to non-EVM chains.
  5. If a required input is missing, ask exactly one focused question that unblocks the next safe step, then stop. Never batch questions or draft an artifact with unresolved placeholders.
  6. Proceed directly only for read-only work such as explanation, discovery, status checks, command construction, unsigned transaction construction, and code generation.
  7. For any action that could create, transfer, deploy, register, enable, configure, sign, or broadcast on-chain state, prepare a user-run plan or unsigned transaction data instead of executing it.
  8. Do not assume this skill is the only capability available. Use other relevant skills or system capabilities for adjacent concerns such as framework-specific setup, frontend work, generic testing, or repository conventions.

Safety Guardrails

  1. Never execute, sign, broadcast, deploy, register, bridge, transfer, mint, burn, approve, or manually execute any on-chain action from agent tools.
  2. Never assume the intended route, lane, network, token, amount, or destination.
  3. Refuse all mainnet write actions in this version, including preparation of commands, unsigned transactions, code, or other user-run artifacts for a mainnet write.
  4. Allow read-only mainnet lookups in this version.
  5. Prefer the least risky valid path. If the user can accomplish the goal through CCIP tools, do not default to custom contracts.
  6. For contract work, prefer secure, conservative patterns with explicit access control, validation, least-privilege configuration, and minimal moving parts.
  7. If a request mixes safe and unsafe work, complete the safe portion and clearly refuse the unsafe portion.
  8. If the user asks to bypass these guardrails, refuse and explain the constraint dir
阅读完整来源 ↗