Back to Details

chainlink-ccip-skill

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Chainlink CCIP Skill

Chainlink CCIP Skill

Overview

概述

Route CCIP requests to the simplest valid path while keeping side effects tightly controlled.
将CCIP请求路由至最简单的有效路径，同时严格控制副作用。

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-mcp.md only when the 
    ccip_sdk
    MCP tool is available and the request can be fulfilled by it for monitoring, discovery, or SDK method calls.
  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, or any non-EVM chain family.
  14. Do not load reference files speculatively.
  1. 以此文件作为默认指南。
  2. 仅当需要具体参考示例（如预检摘要、监控说明、合约生成结构）时，才阅读references/examples.md。
  3. 仅当答案依赖CCIP实时信息、当前工具行为、路由或代币可用性、消息状态界面时，才阅读references/official-sources.md。
  4. 仅当
    ccip_sdk
    MCP工具可用，且请求可通过该工具完成监控、发现或SDK方法调用时，才阅读references/ccip-mcp.md。
  5. 仅当用户希望通过CCIP CLI、API或SDK实现工具优先的工作流时，才阅读references/ccip-tools.md。
  6. 仅当用户需要发送方/接收方合约、代币转账合约、可编程代币转账合约或合约配置帮助时，才阅读references/ccip-contracts.md。
  7. 仅当用户希望创建代币、将其注册为CCT、配置池、设置速率限制或添加CCT运行所需网络时，才阅读references/ccip-cct.md。
  8. 仅当用户希望对CCIP合约进行本地模拟、本地测试或分叉环境测试时，才阅读references/chainlink-local.md。
  9. 仅当用户需要消息查询、监控、状态说明、通道性能分析或失败消息诊断时，才阅读references/ccip-monitoring.md。
  10. 仅当用户需要路由连通性检查、网络分类或支持代币发现时，才阅读references/ccip-discovery.md。
  11. 仅当生成或审核CCIP Solidity合约，且需要具体代码模式（发送方、接收方、代币转账、防御性接收方）时，才阅读references/ccip-solidity-examples.md。
  12. 仅当用户需要TypeScript SDK使用示例（如费用估算、代币转账、消息传递、状态检查）时，才阅读references/ccip-sdk-examples.md。
  13. 仅当用户希望在Solana、Aptos、Sui、TON或任何非EVM链生态中使用CCIP时，才阅读references/ccip-non-evm.md。
  14. 请勿投机性加载参考文件。

Routing

路由规则

  1. Use a tool-first path for sending without custom contracts, bridging funds, status lookup, connectivity checks, and route or token discovery.
  2. When the 
    ccip_sdk
    MCP tool is available, prefer it over direct CLI or SDK invocation for monitoring, discovery, and programmatic SDK method calls. Fall back to CLI or SDK when the tool is not available.
  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), 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. Ask one focused question if the route, network, token, amount, or target contracts are missing.
  6. Proceed without approval only for read-only work such as explanation, discovery, status checks, and code generation.
  7. Trigger the approval protocol before any action that could create, transfer, deploy, register, enable, or configure on-chain state.
  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.
  1. 对于无需自定义合约的发送操作、资金桥接、状态查询、连通性检查以及路由/代币发现，采用工具优先路径。
  2. 当
    ccip_sdk
    MCP工具可用时，优先使用它进行监控、发现和程序化SDK方法调用；工具不可用时，再退而使用CLI或SDK。
  3. 对于发送方与接收方合约开发以及CCT配置流程，采用合约优先路径。
  4. 针对非EVM链请求（Solana、Aptos、Sui、TON），路由至非EVM参考文件获取工作流指导。请勿将EVM特定模式（Solidity、Foundry、Hardhat、Chainlink Local）应用于非EVM链。
  5. 若缺少路由、网络、代币、金额或目标合约信息，提出一个聚焦的问题。
  6. 仅在只读工作（如解释、发现、状态检查、代码生成）中无需批准即可进行。
  7. 在任何可能创建、转移、部署、注册、启用或配置链上状态的操作前，触发批准流程。
  8. 请勿假设本技能是唯一可用的能力。对于框架特定配置、前端开发、通用测试或仓库规范等相关问题，使用其他相关技能或系统能力。

Safety Guardrails

安全防护规则

  1. Never execute any on-chain action without explicit user approval.
  2. Never assume the intended route, lane, network, token, amount, or destination.
  3. Refuse all mainnet write actions in this version.
  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 directly.
  1. 未经用户明确批准，绝不执行任何链上操作。
  2. 绝不假设预期的路由、通道、网络、代币、金额或目的地。
  3. 本版本拒绝所有主网写入操作。
  4. 本版本允许主网只读查询。
  5. 优先选择风险最低的有效路径。若用户可通过CCIP工具完成目标，请勿默认使用自定义合约。
  6. 对于合约开发，优先采用安全、保守的模式，包括明确的访问控制、验证、最小权限配置和最少的可移动组件。
  7. 若请求包含安全与不安全的工作内容，完成安全部分，并明确拒绝不安全部分。
  8. 若用户要求绕过这些防护规则，直接拒绝并解释限制原因。

Approval Protocol

批准流程

Before any on-chain action, present a short preflight summary that includes:
  1. action type
  2. network type
  3. source chain
  4. destination chain
  5. route or lane details if known
  6. token and amount if applicable
  7. whether the action sends data, tokens, or both
  8. contract addresses involved if applicable
  9. tool or method to be used
  10. expected effect
End the preflight with a direct approval question.
Use this structure:
text
Proposed on-chain action:
- Action: ...
- Network: ...
- Source chain: ...
- Destination chain: ...
- Route/lane: ...
- Token/amount: ...
- Payload: ...
- Contracts: ...
- Method: ...
- Expected effect: ...

Do you want me to execute this?
在执行任何链上操作前，提供简短的预检摘要，内容包括：
  1. 操作类型
  2. 网络类型
  3. 源链
  4. 目标链
  5. 已知的路由或通道详情
  6. 适用的代币及金额
  7. 操作是否发送数据、代币，或两者皆有
  8. 涉及的合约地址（若有）
  9. 将使用的工具或方法
  10. 预期效果
在预检摘要末尾提出明确的批准问题。
使用以下结构：
text
拟执行的链上操作：
- 操作：...
- 网络：...
- 源链：...
- 目标链：...
- 路由/通道：...
- 代币/金额：...
- 负载：...
- 合约：...
- 方法：...
- 预期效果：...

是否执行此操作？

Second Confirmation Rule

二次确认规则

Require a second explicit confirmation immediately before execution for any testnet action that:
  1. sends a CCIP message
  2. transfers or bridges tokens
  3. deploys contracts
  4. creates a token
  5. enables or configures a CCT lane
Do not treat the user's original intent as the second confirmation. Ask again right before the side-effecting step.
对于任何测试网操作，若属于以下类型，在执行前需再次明确确认：
  1. 发送CCIP消息
  2. 转账或桥接代币
  3. 部署合约
  4. 创建代币
  5. 启用或配置CCT通道
请勿将用户的原始意图视为二次确认。在执行产生副作用的步骤前，再次询问。

Working Rules

工作规则

  1. Keep questions narrow and unblock the next safe step.
  2. Explain the chosen path briefly.
  3. Generate code only when code is actually needed.
  4. Keep unsupported or out-of-scope features out of the answer rather than speculating about them.
  1. 提出的问题应聚焦，以推进下一个安全步骤。
  2. 简要说明所选路径。
  3. 仅在确实需要时生成代码。
  4. 答案中排除不支持或超出范围的功能，而非对其进行推测。

Documentation Access

文档访问

This skill references official CCIP documentation URLs throughout its reference files. Whether the model can fetch those URLs depends on the host agent's capabilities.
  1. If WebFetch, a browser tool, or an MCP server that can retrieve documentation is available, use it to fetch the referenced URL before answering.
  2. If no documentation-fetching tool is available, do not silently improvise CCIP patterns from training data alone. Instead:
    • Use the embedded reference content in this skill's reference files as the floor for guidance.
    • Tell the user that live documentation could not be verified.
    • Provide the specific URL so the user can check it directly.
  3. For contract-first workflows where correctness matters most, prefer the concrete examples in references/ccip-solidity-examples.md over generating patterns from memory.
本技能在参考文件中引用了官方CCIP文档URL。模型能否获取这些URL取决于宿主Agent的能力。
  1. 若WebFetch、浏览器工具或可检索文档的MCP服务器可用，在回答前先获取引用的URL内容。
  2. 若无文档检索工具可用，请勿仅凭训练数据随意构建CCIP模式。应：
    • 以本技能参考文件中的嵌入式参考内容作为指导基础。
    • 告知用户无法验证实时文档。
    • 提供具体URL，以便用户自行查看。
  3. 对于正确性至关重要的合约优先工作流，优先使用references/ccip-solidity-examples.md中的具体示例，而非凭记忆生成模式。

MCP Recommendations

MCP推荐

This skill works best when the Chainlink MCP server (
@chainlink/mcp-server
) is connected. It provides live access to CCIP message status, lane data, and SDK methods through the 
ccip_sdk
tool.
When the Chainlink MCP server is not available, the Context7 MCP server (
@upstash/context7-mcp
) is a useful fallback for fetching current Chainlink documentation. It can retrieve content from 
docs.chain.link
and other public documentation sources, covering the gap for contract patterns, tutorials, and API references that this skill cannot embed in full.
当连接Chainlink MCP服务器（
@chainlink/mcp-server
）时，本技能的效果最佳。它可通过
ccip_sdk
工具提供CCIP消息状态、通道数据和SDK方法的实时访问。
当Chainlink MCP服务器不可用时，Context7 MCP服务器（
@upstash/context7-mcp
）是获取最新Chainlink文档的实用替代方案。它可从
docs.chain.link
和其他公开文档源检索内容，弥补本技能无法完整嵌入的合约模式、教程和API参考的缺口。