chainlink-ccip-skill

Category: Tools & Productivity | Uploader: smartcontractkit | Downloads: 0 | Version: v1.0（Latest）

Handle Chainlink CCIP requests with a safety-first workflow. Use for CCIP message sends, fund bridging through CCIP tools, sender and receiver contract development, message status lookup, route connectivity checks, supported token discovery, or CCT setup. Ask for missing route details, require explicit approval before any on-chain action, refuse mainnet writes in this version, and prefer secure, conservative contract patterns.

Changelog: Source: GitHub https://github.com/smartcontractkit/chainlink-agent-skills

Directory Structure

Current level: tree/main/chainlink-ccip-skill/

📁 agents/
- 📄 openai.yaml 104 B
📁 references/
- 📄 ccip-cct.md 6.5 KB
- 📄 ccip-contracts.md 9.7 KB
- 📄 ccip-discovery.md 4.9 KB
- 📄 ccip-mcp.md 10.5 KB
- 📄 ccip-monitoring.md 7.0 KB
- 📄 ccip-tools.md 5.9 KB
- 📄 chainlink-local.md 6.6 KB
- 📄 official-sources.md 2.7 KB
- 📄 user-stories.md 3.2 KB
📄 SKILL.md 5.6 KB

SKILL.md

---
name: chainlink-ccip-skill
description: "Handle Chainlink CCIP requests with a safety-first workflow. Use for CCIP message sends, fund bridging through CCIP tools, sender and receiver contract development, message status lookup, route connectivity checks, supported token discovery, or CCT setup. Ask for missing route details, require explicit approval before any on-chain action, refuse mainnet writes in this version, and prefer secure, conservative contract patterns."
license: MIT
compatibility: Designed for AI agents that implement https://agentskills.io/specification, including Claude Code, Cursor Composer, and Codex-style workflows.
metadata:
  version: "0.0.2"
  mcp-server: "@chainlink/mcp-server"
---

# Chainlink CCIP Skill

## Overview

Route CCIP requests to the simplest valid path while keeping side effects tightly controlled.

## Progressive Disclosure

1. Keep this file as the default guide.
2. Read [references/user-stories.md](references/user-stories.md) only when the request is ambiguous or you need routing examples.
3. Read [references/official-sources.md](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](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](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](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](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](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](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](references/ccip-discovery.md) only when the user wants route connectivity checks, network classification, or supported-token discovery.
11. Do not load reference files speculatively.

## 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. Ask one focused question if the route, network, token, amount, or target contracts are missing.
5. Proceed without approval only for read-only work such as explanation, discovery, status checks, and code generation.
6. Trigger the approval protocol before any action that could create, transfer, deploy, register, enable, or configure on-chain state.
7. 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 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.

## 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?
```

## 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.

## 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.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

chainlink-ccip-skill

Directory Structure

SKILL.md

Report

Notice