Agent skill

Multichain Deployment

by ccashwell in ccashwell/evm-cortex

A skill your agent uses when deploying the same protocol to multiple chains at the same address.

MITAuto-check passedDevOps & Cloud

Install Multichain Deployment

skills CLI
$ npx skills add ccashwell/evm-cortex --skill multichain-deployment -a claude-code

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

GitHub CLI
$ gh skill install ccashwell/evm-cortex multichain-deployment --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/ccashwell/evm-cortex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/multichain-deployment .claude/skills/multichain-deployment && 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
multichain-deployment
GitHub stars
131
Token cost
~1.9k tokens
SKILL.md length
166 words
Files
1
Skills in repo
89
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when deploying the same protocol to multiple chains at the same address.

  • Deploying the same protocol to multiple chains at the same address
  • SKILL.md covers Strategy Overview, Deterministic Deployment Factory, Multi-Chain Forge Script and Deployment Registry, plus 4 more sections
  • Needs DEPLOYER_PRIVATE_KEY
  • Tasks that involve Deployment

What it does

Multichain Deployment is an agent skill from ccashwell/evm-cortex. Use when deploying the same protocol to multiple chains at the same address. Covers CREATE2 for deterministic addresses, deployment registries, chain-specific configuration, multi-chain testing, and canonical deployment patterns.

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

It sits in DevOps & Cloud, covering Deployment. The repository describes itself as: Ethereum protocol engineering squad for AI coding assistants. The licence is MIT.

When your agent uses it

  • Deploying the same protocol to multiple chains at the same address
  • Tasks that involve Deployment

Example prompts

  • “/multichain-deployment”

Requirements

  • A credential in DEPLOYER_PRIVATE_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit f8f3301. 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, bash and json).

    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:

    • DEPLOYER_PRIVATE_KEY

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

Context cost

Multichain Deployment loads about 1.9k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 166 words of instructions outside code blocks.

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

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 ccashwell/evm-cortex at commit f8f3301, republished under its MIT licence (© ccashwell). 166 words, ~1,911 tokens.

Download SKILL.mdSave it as .claude/skills/multichain-deployment/SKILL.md (or your agent's skills folder).
name
multichain-deployment
description
Use when deploying the same protocol to multiple chains at the same address. Covers CREATE2 for deterministic addresses, deployment registries, chain-specific configuration, multi-chain testing, and canonical deployment patterns.

Multi-Chain Deployment Patterns

Strategy Overview

For protocol credibility and UX, deploy contracts at the same address on every chain. This requires deterministic deployment via CREATE2 and a consistent deployment flow.

Deterministic Deployment Factory

Use a pre-deployed CREATE2 factory that exists at the same address on all EVM chains.

Arachnid's Deterministic Deployment Proxy (available on nearly all chains):

0x4e59b44847b379578588920cA78FbF26c0B4956C
solidity
// Deploy via the keyless CREATE2 factory
function deployDeterministic(bytes memory creationCode, bytes32 salt)
    external returns (address deployed)
{
    address factory = 0x4e59b44847b379578588920cA78FbF26c0B4956C;
    bytes memory payload = abi.encodePacked(salt, creationCode);
    (bool ok, bytes memory result) = factory.call(payload);
    require(ok, "Deploy failed");
    deployed = address(uint160(uint256(keccak256(abi.encodePacked(
        bytes1(0xff), factory, salt, keccak256(creationCode)
    )))));
}

Multi-Chain Forge Script

solidity
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import {Script, console2} from "forge-std/Script.sol";
import {MyProtocol} from "../src/MyProtocol.sol";

contract MultiChainDeploy is Script {
    address constant CREATE2_FACTORY = 0x4e59b44847b379578588920cA78FbF26c0B4956C;
    bytes32 constant SALT = keccak256("myprotocol-v1.0.0");

    struct ChainConfig {
        string rpc;
        uint256 chainId;
        address admin;
        address weth;
    }

    function configs() internal view returns (ChainConfig[] memory) {
        ChainConfig[] memory c = new ChainConfig[](4);
        address admin = vm.envAddress("ADMIN_ADDRESS");

        c[0] = ChainConfig("mainnet", 1, admin, 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2);
        c[1] = ChainConfig("base", 8453, admin, 0x4200000000000000000000000000000000000006);
        c[2] = ChainConfig("optimism", 10, admin, 0x4200000000000000000000000000000000000006);
        c[3] = ChainConfig("arbitrum", 42161, admin, 0x82aF49447D8a07e3bd95BD0d56f35241523fBab1);
        return c;
    }

    function predictAddress() public view returns (address) {
        bytes memory initCode = type(MyProtocol).creationCode;
        return address(uint160(uint256(keccak256(abi.encodePacked(
            bytes1(0xff), CREATE2_FACTORY, SALT, keccak256(initCode)
        )))));
    }

    function run() external {
        uint256 deployerKey = vm.envUint("DEPLOYER_PRIVATE_KEY");
        ChainConfig[] memory chains = configs();
        address predicted = predictAddress();

        console2.log("Predicted address:", predicted);

        for (uint256 i = 0; i < chains.length; i++) {
            console2.log("\n--- Deploying to", chains[i].rpc, "---");
            vm.createSelectFork(chains[i].rpc);

            if (predicted.code.length > 0) {
                console2.log("  Already deployed, skipping");
                continue;
            }

            vm.startBroadcast(deployerKey);

            bytes memory initCode = type(MyProtocol).creationCode;
            bytes memory payload = abi.encodePacked(SALT, initCode);
            (bool ok,) = CREATE2_FACTORY.call(payload);
            require(ok, "Deploy failed");
            require(predicted.code.length > 0, "Code not at predicted address");

            console2.log("  Deployed at:", predicted);

            // Chain-specific initialization
            MyProtocol(predicted).initialize(chains[i].admin, chains[i].weth);

            vm.stopBroadcast();
        }
    }
}
bash
forge script script/MultiChainDeploy.s.sol --broadcast --multi --verify

Deployment Registry

Track deployments across chains:

json
{
  "protocol": "MyProtocol",
  "version": "1.0.0",
  "salt": "0x...",
  "deployments": {
    "1": {
      "address": "0xSameOnAllChains",
      "txHash": "0x...",
      "blockNumber": 18000000,
      "deployer": "0x...",
      "timestamp": "2025-06-01T00:00:00Z"
    },
    "8453": {
      "address": "0xSameOnAllChains",
      "txHash": "0x...",
      "blockNumber": 5000000,
      "deployer": "0x...",
      "timestamp": "2025-06-01T00:05:00Z"
    }
  }
}

Generate automatically in your deploy script:

solidity
function _writeDeployment(uint256 chainId, address deployed, bytes32 txHash) internal {
    string memory key = vm.toString(chainId);
    string memory json = vm.serializeAddress(key, "address", deployed);
    json = vm.serializeBytes32(key, "txHash", txHash);
    json = vm.serializeUint(key, "blockNumber", block.number);
    vm.writeJson(json, "./deployments.json", string.concat(".", key));
}

Chain-Specific Configuration

When contracts need different config per chain but the same address:

solidity
contract MyProtocol {
    address public admin;
    address public weth;
    bool private _initialized;

    function initialize(address admin_, address weth_) external {
        require(!_initialized, "Already initialized");
        _initialized = true;
        admin = admin_;
        weth = weth_;
    }
}

For CREATE3 (address independent of constructor args):

solidity
import {CREATE3} from "solady/utils/CREATE3.sol";

contract MultiChainFactory {
    function deploy(bytes32 salt, bytes memory creationCode) external returns (address) {
        return CREATE3.deploy(salt, creationCode, 0);
    }

    function predict(bytes32 salt) external view returns (address) {
        return CREATE3.getDeployed(salt);
    }
}

Multi-Chain Testing

solidity
contract MultiChainTest is Test {
    uint256 mainnetFork;
    uint256 baseFork;
    uint256 opFork;

    function setUp() public {
        mainnetFork = vm.createFork("mainnet");
        baseFork = vm.createFork("base");
        opFork = vm.createFork("optimism");
    }

    function test_deploysSameAddress() public {
        bytes32 salt = keccak256("test-v1");
        bytes memory initCode = type(MyProtocol).creationCode;

        vm.selectFork(mainnetFork);
        address addrMainnet = _deployViaCreate2(salt, initCode);

        vm.selectFork(baseFork);
        address addrBase = _deployViaCreate2(salt, initCode);

        vm.selectFork(opFork);
        address addrOp = _deployViaCreate2(salt, initCode);

        assertEq(addrMainnet, addrBase, "Mainnet != Base");
        assertEq(addrBase, addrOp, "Base != Optimism");
    }
}

Verification Across Chains

bash
#!/bin/bash
# verify-all.sh

CHAINS=("mainnet" "base" "optimism" "arbitrum")
CONTRACT_ADDR="0xSameOnAllChains"
CONTRACT_PATH="src/MyProtocol.sol:MyProtocol"

for chain in "${CHAINS[@]}"; do
  echo "Verifying on $chain..."
  forge verify-contract "$CONTRACT_ADDR" "$CONTRACT_PATH" \
    --chain "$chain" --watch
done

Multi-Chain Deployment Checklist

  • Same CREATE2 factory exists on all target chains
  • Salt is unique per protocol version
  • Init code is identical (same compiler, settings, no chain-specific constructor args)
  • Predicted address verified before deployment
  • Idempotent script (skips chains already deployed)
  • Chain-specific config applied via initialize (not constructor)
  • Deployment registry updated after each chain
  • Contracts verified on each chain's block explorer
  • Cross-chain functionality tested (bridges, messaging)
  • Admin/governance addresses correct per chain

© ccashwell, MIT. 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 skills/multichain-deployment of ccashwell/evm-cortex.

Open the folder on GitHubat commit f8f3301

Compare with similar skills

Multichain Deployment 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.

Multichain Deployment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Multichain Deployment this skillccashwell/evm-cortex131—~1.9kAutomated safety check: PassMIT
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
KubeSphere ServiceMesh Managerkubesphere/kubesphere17k—~2.4kAutomated safety check: PassCustom licence
Vercelremotion-dev/remotion62k—~1.2kAutomated safety check: PassCustom licence
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT

Similar skills

  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • KubeSphere ServiceMesh Manager

    kubesphere/kubesphere

    Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.

    17k GitHub stars~2.4k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Vercel

    remotion-dev/remotion

    Official

    Set up a Codex monitor for Vercel deployments and preview URLs.

    62k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

More from ccashwell/evm-cortex

All 89 skills in this repo
  • Xray Pre Audit

    ccashwell/evm-cortex

    A skill your agent uses when preparing for a security audit, performing reconnaissance on a new codebase, or creating a protocol overview.

    131 GitHub stars~25k tokensUpdated 8 days ago
    Auto-check passed
  • Aave Integration

    ccashwell/evm-cortex

    A skill your agent uses when integrating with Aave V3 for lending, borrowing, flash loans, or building on top of Aave markets.

    131 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed
  • Access Control Patterns

    ccashwell/evm-cortex

    Access control design patterns for Solidity protocols. An agent skill from ccashwell/evm-cortex.

    131 GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed
  • Anvil Patterns

    ccashwell/evm-cortex

    A skill your agent uses when running a local Ethereum node with Anvil.

    131 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed
  • Audit Breadth Scan

    ccashwell/evm-cortex

    A skill your agent uses when performing systematic breadth-first review of all contracts during a security audit.

    131 GitHub stars~1.4k tokensUpdated 8 days ago
    Auto-check passed
  • Audit Depth Analysis

    ccashwell/evm-cortex

    A skill your agent uses when performing deep analysis of specific findings or high-risk areas during a security audit.

    131 GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed

Categories

Questions about Multichain Deployment

What does Multichain Deployment do?

A skill your agent uses when deploying the same protocol to multiple chains at the same address. Multichain Deployment is an agent skill from ccashwell/evm-cortex. Use when deploying the same protocol to multiple chains at the same address.

When should I use Multichain Deployment?

Multichain Deployment fits situations like: deploying the same protocol to multiple chains at the same address; tasks that involve Deployment.

How do I install Multichain Deployment in Claude Code?

Run `npx skills add ccashwell/evm-cortex --skill multichain-deployment -a claude-code`. Or copy the skill folder (skills/multichain-deployment in ccashwell/evm-cortex) into .claude/skills/multichain-deployment in your project. Claude Code loads it when a task matches its description.

How do I install Multichain Deployment in Codex?

Run `npx skills add ccashwell/evm-cortex --skill multichain-deployment -a codex`. Or copy the skill folder (skills/multichain-deployment in ccashwell/evm-cortex) into .agents/skills/multichain-deployment in your project. Codex loads it when a task matches its description.

Can I use Multichain Deployment 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 ccashwell/evm-cortex --skill multichain-deployment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/multichain-deployment, .gemini/skills/multichain-deployment, .github/skills/multichain-deployment and .opencode/skills/multichain-deployment in your project.

What does Multichain Deployment need to run?

Going by SKILL.md and its folder, Multichain Deployment needs credentials named DEPLOYER_PRIVATE_KEY. Our summary lists: A credential in DEPLOYER_PRIVATE_KEY.

Does Multichain Deployment 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 Multichain Deployment 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 Multichain Deployment use?

Multichain Deployment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Multichain Deployment use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 Multichain Deployment?

Skills that share tags, products or a category with Multichain Deployment: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Multichain Deployment?

ccashwell (a GitHub user) maintains it in ccashwell/evm-cortex, which has 131 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on September 30, 2026.

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