Agent skill

Cross Chain Developer

by FerroxLabs in FerroxLabs/wayland

Cross-chain development expertise covering bridge architectures (lock-and-mint, burn-and-mint, liquidity networks), interoperability protocols (LayerZero, Chainlink CCIP, Axelar, Wormhole), chain…

Apache-2.0Auto-check passed

Install Cross Chain Developer

skills CLI
$ npx skills add FerroxLabs/wayland --skill cross-chain-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland cross-chain-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/emerging-tech/cross-chain-developer .claude/skills/cross-chain-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cross-chain-developer
GitHub stars
608
Token cost
~4.1k tokens
SKILL.md length
708 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Cross-chain development expertise covering bridge architectures (lock-and-mint, burn-and-mint, liquidity networks), interoperability protocols (LayerZero, Chainlink CCIP, Axelar, Wormhole), chain…

  • Works in 7 steps: What needs to cross chains? Tokens,… → Which chains? Ethereum, Arbitrum,… → Latency requirements: Is near-instant… → …
  • The user asks about cross chain developer
  • SKILL.md covers When to Use, Questions to Ask the User First, Bridge Architecture Patterns and Messaging Protocols, plus 8 more sections
  • Needs PRIVATE_KEY

What it does

Cross Chain Developer is an agent skill from FerroxLabs/wayland. Cross-chain development expertise covering bridge architectures (lock-and-mint, burn-and-mint, liquidity networks), interoperability protocols (LayerZero, Chainlink CCIP, Axelar, Wormhole), chain abstraction patterns, multi-chain deployment strategies, and security considerations for cross-chain applications. Use when the user asks about cross chain developer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of cross chain developer or requires…

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about cross chain developer
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of cross chain developer

Example prompts

  • “/cross-chain-developer”

Requirements

  • A credential in PRIVATE_KEY

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. What needs to cross chains? Tokens, arbitrary messages, NFTs, or governance actions?
  2. Which chains? Ethereum, Arbitrum, Optimism, Polygon, Base, Solana, or others?
  3. Latency requirements: Is near-instant delivery needed, or is eventual consistency acceptable?
  4. Trust model preference: Fully trustless, optimistic, or committee-based verification?
  5. Volume expectations: Expected message/transfer volume per day?
  6. Existing infrastructure: Are you using any messaging protocol already?
  7. User experience goal: Should users know they are crossing chains, or should it be abstracted?

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are solidity, typescript and template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • PRIVATE_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cross Chain Developer loads about 4.1k tokens when it runs. Until then it costs about 143 tokens; SKILL.md has 708 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 708 words, ~4,105 tokens.

Download SKILL.mdSave it as .claude/skills/cross-chain-developer/SKILL.md (or your agent's skills folder).
name
cross-chain-developer
description
Cross-chain development expertise covering bridge architectures (lock-and-mint, burn-and-mint, liquidity networks), interoperability protocols (LayerZero, Chainlink CCIP, Axelar, Wormhole), chain abstraction patterns, multi-chain deployment strategies, and security considerations for cross-chain applications. Use when the user asks about cross chain developer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of cross chain developer or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
advanced blockchain checklist typescript testing networking safety contracts
metadata.category
emerging-tech
metadata.subcategory
blockchain-web3
metadata.disclaimer
none
metadata.difficulty
intermediate

Cross-Chain Developer

You are an expert cross-chain developer specializing in building applications that operate across multiple blockchain networks. You understand bridge architectures, messaging protocols, chain abstraction, and the unique security challenges of cross-chain systems.

IMPORTANT DISCLAIMER: Cross-chain bridges have been the target of the largest exploits in DeFi history (Ronin $625M, Wormhole $320M, Nomad $190M). Cross-chain development requires extreme security rigor. Always use battle-tested protocols and engage specialist auditors.

When to Use

Use this skill when:

  • User asks about cross chain developer techniques or best practices
  • User needs guidance on cross chain developer concepts
  • User wants to implement or improve their approach to cross chain developer

Do NOT use when:

  • The request falls outside the scope of cross chain developer
  • User needs a different specialized skill for their specific situation
  • The topic requires professional consultation beyond general guidance

Questions to Ask the User First

  1. What needs to cross chains? Tokens, arbitrary messages, NFTs, or governance actions?
  2. Which chains? Ethereum, Arbitrum, Optimism, Polygon, Base, Solana, or others?
  3. Latency requirements: Is near-instant delivery needed, or is eventual consistency acceptable?
  4. Trust model preference: Fully trustless, optimistic, or committee-based verification?
  5. Volume expectations: Expected message/transfer volume per day?
  6. Existing infrastructure: Are you using any messaging protocol already?
  7. User experience goal: Should users know they are crossing chains, or should it be abstracted?

Bridge Architecture Patterns

Lock-and-Mint
Source Chain                          Destination Chain
┌──────────────┐                    ┌──────────────┐
│ User locks   │   Verification    │ Bridge mints │
│ 100 USDC in  │ ──────────────>  │ 100 bUSDC to │
│ bridge vault │   (relayer/proof) │ user address  │
└──────────────┘                    └──────────────┘

On return: burn bUSDC on destination, unlock USDC on source

Tradeoffs: Original asset stays on source (canonical), but wrapped token has bridge-specific risk. If bridge is exploited, wrapped tokens become worthless.

Burn-and-Mint (Native Cross-Chain Tokens)
Source Chain                          Destination Chain
┌──────────────┐                    ┌──────────────┐
│ Token burned  │   Attestation    │ Token minted │
│ on source    │ ──────────────>  │ on dest      │
│ (supply -= n)│   (oracle network)│ (supply += n)│
└──────────────┘                    └──────────────┘

Total supply across all chains remains constant

Use case: CCTP (Circle's Cross-Chain Transfer Protocol) for native USDC transfers. No wrapped tokens needed.

Liquidity Network (Atomic Swaps)
Source Chain                          Destination Chain
┌──────────────┐                    ┌──────────────┐
│ User sends to│   Liquidity pool  │ LP sends to  │
│ LP on source │ <──────────────> │ user on dest  │
│              │   Rebalancing     │              │
└──────────────┘                    └──────────────┘

No wrapped tokens -- native assets on both sides

Examples: Stargate, Across Protocol. Fast but limited by LP depth.

Decision Framework
FactorLock-and-MintBurn-and-MintLiquidity Network
Speed10-30 min10-30 min1-10 min
Token typeWrappedNativeNative
Capital efficiencyHighHighLow (needs LP)
Trust modelBridge dependentOracle networkEconomic incentives
Best forGeneric token bridgingStablecoin issuersFast transfers

Messaging Protocols

LayerZero V2
solidity
// Sending a cross-chain message with LayerZero V2
import { OApp, Origin, MessagingFee } from "@layerzerolabs/oapp-evm/contracts/oapp/OApp.sol";

contract CrossChainCounter is OApp {
    uint256 public count;

    constructor(address _endpoint, address _delegate) OApp(_endpoint, _delegate) {}

    // Send increment message to another chain
    function incrementRemote(
        uint32 _dstEid,      // destination endpoint ID
        bytes calldata _options
    ) external payable {
        bytes memory payload = abi.encode(count + 1);
        _lzSend(
            _dstEid,
            payload,
            _options,
            MessagingFee(msg.value, 0),
            payable(msg.sender)
        );
    }

    // Receive message from another chain
    function _lzReceive(
        Origin calldata _origin,
        bytes32 _guid,
        bytes calldata _message,
        address _executor,
        bytes calldata _extraData
    ) internal supersede {
        count = abi.decode(_message, (uint256));
    }

    // Quote the fee for sending
    function quote(
        uint32 _dstEid,
        bytes calldata _options
    ) external view returns (MessagingFee memory) {
        return _quote(_dstEid, abi.encode(count + 1), _options, false);
    }
}
solidity
import {IRouterClient} from "@chainlink/contracts-ccip/src/v0.8/ccip/interfaces/IRouterClient.sol";
import {Client} from "@chainlink/contracts-ccip/src/v0.8/ccip/libraries/Client.sol";
import {CCIPReceiver} from "@chainlink/contracts-ccip/src/v0.8/ccip/applications/CCIPReceiver.sol";

contract CrossChainSender {
    IRouterClient public router;
    IERC20 public linkToken;

    function sendMessage(
        uint64 destinationChainSelector,
        address receiver,
        bytes calldata data
    ) external returns (bytes32 messageId) {
        Client.EVM2AnyMessage memory message = Client.EVM2AnyMessage({
            receiver: abi.encode(receiver),
            data: data,
            tokenAmounts: new Client.EVMTokenAmount[](0),
            feeToken: address(linkToken),
            extraArgs: Client._argsToBytes(
                Client.EVMExtraArgsV1({gasLimit: 200_000})
            )
        });

        uint256 fees = router.getFee(destinationChainSelector, message);
        linkToken.approve(address(router), fees);
        messageId = router.ccipSend(destinationChainSelector, message);
    }
}

contract CrossChainReceiver is CCIPReceiver {
    constructor(address _router) CCIPReceiver(_router) {}

    function _ccipReceive(
        Client.Any2EVMMessage memory message
    ) internal supersede {
        address sender = abi.decode(message.sender, (address));
        bytes memory data = message.data;
        // Process cross-chain message
    }
}
Protocol Comparison
FeatureLayerZero V2Chainlink CCIPAxelarWormhole
VerificationDVN (configurable)DON (Chainlink oracles)Validator setGuardian set
Chains supported50+20+50+30+
Token transfersOFT standardNative token poolsGMP + ITSPortal bridge
Message formatBytes payloadStructured EVM2AnyGMP bytesVAA bytes
Fee tokenNative gasLINK or nativeAXL or nativeNative gas
Finality modelConfigurableWait for finalityThreshold signaturesGuardian consensus

Multi-Chain Deployment

Deterministic Deployment (Same Address Everywhere)
solidity
// Using CREATE2 via a factory for deterministic addresses
contract DeterministicFactory {
    function deploy(bytes32 salt, bytes calldata bytecode)
        external
        returns (address deployed)
    {
        assembly {
            deployed := create2(0, add(bytecode, 0x20), mload(bytecode), salt)
        }
        require(deployed != address(0), "Deploy failed");
    }
}

// Pre-compute the address
function computeAddress(bytes32 salt, bytes32 bytecodeHash)
    external view returns (address)
{
    return address(uint160(uint256(keccak256(abi.encodePacked(
        bytes1(0xff),
        address(this),
        salt,
        bytecodeHash
    )))));
}
Deployment Script (Foundry Multi-Chain)
solidity
// script/DeployMultiChain.s.sol
contract DeployMultiChain is Script {
    function run() external {
        // Deploy to each chain using fork URLs
        string[3] memory chains = ["ethereum", "arbitrum", "base"];
        address[3] memory endpoints; // LayerZero endpoints per chain

        for (uint i = 0; i < chains.length; i++) {
            vm.createSelectFork(vm.envString(
                string.concat("RPC_", chains[i])
            ));
            vm.startBroadcast(vm.envUint("PRIVATE_KEY"));

            MyOApp app = new MyOApp{salt: bytes32("v1")}(
                endpoints[i],
                vm.envAddress("OWNER")
            );

            vm.stopBroadcast();
        }
    }
}
Configuration Management
typescript
// hardhat.config.ts multi-chain setup
const config: HardhatUserConfig = {
  networks: {
    ethereum: { url: CONFIG.ETH_RPC, chainId: 1 },
    arbitrum: { url: CONFIG.ARB_RPC, chainId: 42161 },
    optimism: { url: CONFIG.OP_RPC, chainId: 10 },
    base:     { url: CONFIG.BASE_RPC, chainId: 8453 },
    polygon:  { url: CONFIG.POLY_RPC, chainId: 137 },
  }
};

// Deployment registry -- track addresses across chains
// deploy-registry.json
{
  "MyOApp": {
    "1":     "0xabc...123",
    "42161": "0xabc...123",  // same address via CREATE2
    "10":    "0xabc...123",
    "8453":  "0xabc...123"
  }
}

Chain Abstraction Patterns

Intent-Based Architecture
User Intent: "Swap 100 USDC on Arbitrum for ETH on Base"

┌─────────────┐     ┌──────────────┐     ┌─────────────┐
│ User signs  │────>│ Solver fills │────>│ Settlement  │
│ intent      │     │ order cross- │     │ verifies    │
│ (off-chain) │     │ chain        │     │ fulfillment │
└─────────────┘     └──────────────┘     └─────────────┘

Benefits: User doesn't choose bridge, solver optimizes routing
Examples: Across, UniswapX, Socket
Account Abstraction + Cross-Chain
Single Account, Multi-Chain:
- User has one smart account address (same on all EVM chains)
- Paymaster sponsors gas on destination chain
- Session keys allow automated cross-chain operations
- Bundler submits UserOperations on appropriate chain

ERC-4337 + Cross-chain:
1. User signs UserOp on source chain
2. Bundler detects cross-chain intent
3. Message sent via bridge protocol
4. Destination bundler executes corresponding UserOp

Cross-Chain Security

Critical Security Considerations
1. Message Replay Protection
   - Include source chain ID in message payload
   - Track processed message IDs (nonce or hash)
   - Verify source chain and sender address

2. Finality Requirements
   - Ethereum: wait 12-15 minutes (finalized epoch)
   - Arbitrum/Optimism: 7-day challenge period for full security
   - Fast confirmations trade security for speed

3. Trust Model Assessment
   Questions for every bridge integration:
   - How many validators/guardians must collude to forge a message?
   - What is the economic security (stake at risk)?
   - Is there a fraud proof mechanism?
   - What happens if the bridge is paused?

4. Rate Limiting
   - Cap maximum transfer size per transaction
   - Cap maximum volume per time window
   - Implement circuit breakers for anomalous activity
Show full SKILL.md (283 more words)Show less
Anti-Pattern: Trusting msg.sender on Destination
solidity
// WRONG: msg.sender on destination is the bridge relayer, not the user
function receiveMessage(bytes calldata data) external {
    require(msg.sender == trustedRelayer);  // relayer, not original sender
    (address user, uint256 amount) = abi.decode(data, (address, uint256));
    // Must verify 'user' was the actual sender on source chain
}

// CORRECT: Verify the cross-chain origin
function _ccipReceive(Client.Any2EVMMessage memory message) internal supersede {
    // Verify source chain
    require(isAllowedChain[message.sourceChainSelector], "Unknown chain");
    // Verify source sender (the contract on the other chain)
    address sourceSender = abi.decode(message.sender, (address));
    require(sourceSender == trustedRemoteContract, "Unknown sender");
    // Now safe to process
}
Testing Cross-Chain Applications
solidity
// Foundry fork testing for cross-chain
contract CrossChainTest is Test {
    uint256 ethFork;
    uint256 arbFork;

    function setUp() public {
        ethFork = vm.createFork("ETH_RPC_URL");
        arbFork = vm.createFork("ARB_RPC_URL");
    }

    function test_crossChainTransfer() public {
        // Step 1: Send on Ethereum
        vm.selectFork(ethFork);
        vm.prank(user);
        sourceBridge.send{value: fee}(arbChainId, amount, user);

        // Step 2: Simulate message delivery on Arbitrum
        vm.selectFork(arbFork);
        // Manually call receive with expected payload
        vm.prank(address(arbRelayer));
        destBridge.receiveMessage(
            abi.encode(user, amount),
            ethChainId
        );

        assertEq(destToken.balanceOf(user), amount);
    }
}

Production Checklist

Before Deployment
  • Message replay protection verified across all chain pairs
  • Source chain and sender validation on all receive functions
  • Rate limits and circuit breakers configured
  • Finality assumptions documented and appropriate for value at risk
  • Fallback mechanism if bridge goes offline
  • Gas estimation accounts for destination chain execution
  • All chain-specific configurations (endpoints, selectors) verified
Monitoring and Operations
  • Alert on failed message deliveries
  • Alert on unusual volume or large transfers
  • Dashboard tracking pending cross-chain messages
  • Runbook for manual message retry/recovery
  • Bridge protocol status monitoring (is the bridge operational?)

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to cross chain developer
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Cross Chain Developer Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with cross chain developer for my current situation"

Output:

Based on your situation, here is a structured approach to cross chain developer:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/emerging-tech/cross-chain-developer of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Cross Chain Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cross Chain Developer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cross Chain Developer this skillFerroxLabs/wayland608—~4.1kAutomated safety check: PassApache-2.0
Architecture Patternswshobson/agents40k—~2kAutomated safety check: PassMIT
Android Clean Architectureaffaan-m/ECC274k4 repos~2.2kAutomated safety check: PassMIT
Architecture Patternsdavila7/claude-code-templates32k4 repos~483Automated safety check: PassMIT
Architecture Docs Writerprisma/orm48k—~1.6kAutomated safety check: PassApache-2.0
Architecture Decision Recordsaffaan-m/ECC274k4 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Architecture Patterns

    wshobson/agents

    Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

    40k GitHub stars~2k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Applies Clean Architecture to Android and Kotlin Multiplatform projects: module layout, dependency rules, UseCases, Repositories and data layer patterns.

    274k GitHub starsUsed in 4 repos~2.2k tokens
    DevelopmentAuto-check passed
  • Architecture Patterns

    davila7/claude-code-templates

    Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

    32k GitHub starsUsed in 4 repos~483 tokens
    DevelopmentAuto-check passed
  • Official

    Guides writing and rewriting architecture subsystem docs, ADRs and reference pages so they make sense to a developer with no prior project context.

    48k GitHub stars~1.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.

    274k GitHub starsUsed in 4 repos~1.8k tokens
    DevelopmentAuto-check passed
  • 设计、实现并重构端口与适配器系统,具有清晰的领域边界、依赖反转以及跨 TypeScript、Java、Kotlin 和 Go 服务的可测试用例编排。

    274k GitHub stars~1.6k tokensUpdated 2 days ago
    MobileAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Cross Chain Developer

What does Cross Chain Developer do?

Cross-chain development expertise covering bridge architectures (lock-and-mint, burn-and-mint, liquidity networks), interoperability protocols (LayerZero, Chainlink CCIP, Axelar, Wormhole), chain…. Cross Chain Developer is an agent skill from FerroxLabs/wayland. Cross-chain development expertise covering bridge architectures (lock-and-mint, burn-and-mint, liquidity networks), interoperability protocols (LayerZero, Chainlink CCIP, Axelar, Wormhole), chain abstraction patterns, multi-chain deployment strategies, and security considerations for cross-chain applications.

When should I use Cross Chain Developer?

Cross Chain Developer fits situations like: the user asks about cross chain developer; related techniques; needs guidance in this domain; the request is outside the scope of cross chain developer.

How do I install Cross Chain Developer in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill cross-chain-developer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/emerging-tech/cross-chain-developer in FerroxLabs/wayland) into .claude/skills/cross-chain-developer in your project. Claude Code loads it when a task matches its description.

How do I install Cross Chain Developer in Codex?

Run `npx skills add FerroxLabs/wayland --skill cross-chain-developer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/emerging-tech/cross-chain-developer in FerroxLabs/wayland) into .agents/skills/cross-chain-developer in your project. Codex loads it when a task matches its description.

Can I use Cross Chain Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill cross-chain-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-chain-developer, .gemini/skills/cross-chain-developer, .github/skills/cross-chain-developer and .opencode/skills/cross-chain-developer in your project.

What does Cross Chain Developer need to run?

Going by SKILL.md and its folder, Cross Chain Developer needs credentials named PRIVATE_KEY. Our summary lists: A credential in PRIVATE_KEY.

Does Cross Chain Developer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cross Chain Developer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cross Chain Developer use?

Cross Chain Developer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross Chain Developer use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cross Chain Developer?

Skills that share tags, products or a category with Cross Chain Developer: Architecture Patterns (wshobson/agents, 40k stars), Android Clean Architecture (affaan-m/ECC, 274k stars), Architecture Patterns (davila7/claude-code-templates, 32k stars) and Architecture Docs Writer (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross Chain Developer?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.