chainlink-ccip-skill
Handles Chainlink CCIP requests and never signs or broadcasts. It sends one-node GET diagnosis to chainlink-nop-skill. It sends ACE policy design to chainlink-ace-skill. Pool and message mechanics stay here. It applies to route, token, message-status, and lane lookups, fee estimates, cross-chain transfers and messaging, sender and receiver contracts, extraArgs V3, Fast Transfers, CCT token pools, and CCIP monitoring.
63
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./chainlink-ccip-skill/SKILL.mdW009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
The skill handles Chainlink CCIP operations, cross-chain messaging, transfers, and contract setups. However, it explicitly prohibits executing transactions, signing, or broadcasting, stating: "This skill never signs or sends. You must sign and broadcast from your own wallet" and "Never deploy, register, bridge, transfer, mint, burn, approve, or execute onchain manually" (SKILL.md:38). Because it prepares data/templates for user-run execution without performing direct financial transactions or holding transfer authority itself, it constitutes an indirect operation or guidance framework. Therefore, the financial exposure tier is medium due to indirect operations.
- Repository
smartcontractkit/chainlink-agent-skills
- Revision
b118be5
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.