Skill 06 cross chain bridge
Skill vaquarkhan/web3-agent-skills/skills/skill-06-cross-chain-bridge
Production-grade Agent Skills for Web3 AI agents: 15 workflows, 6 MCP servers, DeFi/NFT/compliance guardrails, and VS Code/JetBrains installers.
npx -y skills add vaquarkhan/web3-agent-skills --skill skill-06-cross-chain-bridgeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Handles cross-chain operations including token bridging, cross-chain messaging, and intent-based routing. Use when moving assets or data between blockchains.
SKILL.md
2.6 KB, as published. Nobody here has run it
Cross-Chain Bridge
When to Use
- Bridging tokens between L1 and L2 or across L2s
- Sending cross-chain messages (LayerZero, Wormhole, CCIP)
- Intent-based cross-chain swaps (Across, Stargate)
- Validating bridge security before large transfers
Prerequisites
- MCP:
blockchain-rpc-server,price-feed-server,compliance-screening-server - Skills: skill-08 (bridge contract verification), skill-09 (screen recipient)
Workflow
1. Bridge Selection
| Bridge | Type | Security Model |
|---|---|---|
| Native (Arbitrum, Optimism) | Canonical | L1 contract + fraud/validity proof |
| Stargate (LayerZero) | Liquidity | Oracle + relayer (configurable) |
| Across | Intent | Optimistic with bonded relayers |
| Wormhole | Messaging | Guardian multisig |
| CCIP (Chainlink) | Messaging | DON + Risk Management Network |
For transfers > $10,000: prefer canonical bridges or CCIP over pure liquidity bridges.
2. Bridge Security Checklist
- Bridge TVL and audit history reviewed
- Contract verified on both source and destination chains
- No active exploit warnings (check Rekt, bridge status pages)
- Estimated time and fees acceptable
- Destination address correct for target chain format
3. Execution
- Approve token on source chain (exact amount)
- Call bridge deposit/send function
- Monitor source tx confirmation
- Track message delivery (LayerZero scan, Wormhole explorer)
- Claim on destination if manual claim required
- Verify received amount matches expected (minus fees)
4. Cross-Chain Messaging
For dApp cross-chain calls:
- Encode payload with target function selector
- Set gas limit on destination via quote
- Pay messaging fee in native token or LINK
- Handle
lzReceive/ccipReceiveon destination
5. Intent-Based Routing
Across and similar protocols:
- User expresses intent (source token → destination token)
- Relayers compete to fill at best rate
- Refund on source if not filled within deadline
Risk Warnings
- Bridge hacks historically largest DeFi losses — verify before large transfers
- Always test with small amount first on new routes
- Never bridge to unverified recipient contracts
References
knowledge-base/chains/— per-chain bridge addressesreferences/bridge-security-matrix.md