Agent skill

Fix Check Superchain Registry

by ethereum-optimism in ethereum-optimism/superchain-ops

Diagnose and fix a failing checksuperchainregistry CircleCI job on superchain-ops, typically caused by the pinned lib/superchain-registry submodule drifting from upstream main.

MITAuto-check passedDevOps & Cloud

Install Fix Check Superchain Registry

skills CLI
$ npx skills add ethereum-optimism/superchain-ops --skill fix-check-superchain-registry -a claude-code

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

GitHub CLI
$ gh skill install ethereum-optimism/superchain-ops fix-check-superchain-registry --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/ethereum-optimism/superchain-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-check-superchain-registry .claude/skills/fix-check-superchain-registry && 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
fix-check-superchain-registry
GitHub stars
99
Token cost
~932 tokens
SKILL.md length
364 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Diagnose and fix a failing checksuperchainregistry CircleCI job on superchain-ops, typically caused by the pinned lib/superchain-registry submodule drifting from upstream main.

  • Works in 5 steps: Get upstream main HEAD SHA. If git… → Before bumping, confirm no in-repo task… → Update the gitlink → …
  • Tasks that involve CI/CD
  • SKILL.md covers What the check does, Fast diagnosis, The fix and Note on strictness /…
  • Calls git, curl and jq; reaches raw.githubusercontent.com and github.com

What it does

Fix Check Superchain Registry is an agent skill from ethereum-optimism/superchain-ops. Diagnose and fix a failing checksuperchainregistry CircleCI job on superchain-ops, typically caused by the pinned lib/superchain-registry submodule drifting from upstream main.

Its SKILL.md is about 930 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 CI/CD. It works with Git and Ethereum. The repository describes itself as: superchain-ops allows builders to create and execute tasks on EVM chains. The licence is MIT.

When your agent uses it

  • Tasks that involve CI/CD

Example prompts

  • “/fix-check-superchain-registry”

Workflow steps

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

  1. Get upstream main HEAD SHA. If git ls-remote / GitHub API are blocked in
  2. Before bumping, confirm no in-repo task references the removed chain IDs
  3. Update the gitlink
  4. Verify only the gitlink changed: git diff --cached --stat should show
  5. Commit and open a PR. CI re-runs the check against the newly pinned commit.

What it can do on your machine

Read from SKILL.md and the folder at commit 7833789. 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

    Shell commands in SKILL.md call:

    • git
    • curl
    • jq
    • just
    • bash

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • raw.githubusercontent.com
    • github.com

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Fix Check Superchain Registry loads about 932 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 364 words of instructions outside code blocks.

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

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 ethereum-optimism/superchain-ops at commit 7833789, republished under its MIT licence (© ethereum-optimism). 364 words, ~932 tokens.

Download SKILL.mdSave it as .claude/skills/fix-check-superchain-registry/SKILL.md (or your agent's skills folder).
name
fix-check-superchain-registry
description
Diagnose and fix a failing `check_superchain_registry` CircleCI job on superchain-ops, typically caused by the pinned lib/superchain-registry submodule drifting from upstream main.

Fix check_superchain_registry CI failure

What the check does

The CI chain is:

  • .circleci/config.yml job check_superchain_registry
  • -> src/ci.just recipe check-superchain-registry-latest
  • -> src/script/check-superchain-latest.sh

The script compares the pinned submodule file lib/superchain-registry/superchain/extra/addresses/addresses.json against the live upstream file at https://raw.githubusercontent.com/ethereum-optimism/superchain-registry/main/superchain/extra/addresses/addresses.json.

For every chain ID present in the pinned file it checks two keys — L1StandardBridgeProxy and SystemConfigProxy — and fails (exit 1) if a key is missing upstream or the addresses mismatch. It emits lines like:

Error: remote missing L1StandardBridgeProxy on chain <ID>

The check is asymmetric: it tolerates upstream having extra chains the pinned file lacks, but hard-fails when the pinned file lists a chain that upstream has removed. So the recurring cause is upstream deleting a chain (e.g. rehearsal/test networks) while our submodule still points at the older commit that includes it.

Fast diagnosis

Reproduce locally without CI:

bash
# Pinned (local submodule) file:
LOCAL=lib/superchain-registry/superchain/extra/addresses/addresses.json

# Live upstream main:
curl -sL "https://raw.githubusercontent.com/ethereum-optimism/superchain-registry/main/superchain/extra/addresses/addresses.json" -o /tmp/remote-addresses.json

# List chain IDs present locally but absent upstream (these are what break the check):
jq -n --slurpfile L "$LOCAL" --slurpfile R /tmp/remote-addresses.json \
  '$L[0] | keys[] | select(($R[0][.]) == null)'

Or just run the check itself: just check-superchain-registry-latest (or bash src/script/check-superchain-latest.sh). The Error: remote missing ... lines name the offending chain IDs.

The fix

Bump the lib/superchain-registry submodule to current upstream main. This is a one-line gitlink change.

  1. Get upstream main HEAD SHA. If git ls-remote / GitHub API are blocked in your environment, the commits page or its .atom feed (https://github.com/ethereum-optimism/superchain-registry/commits/main.atom) expose the SHA, and raw.githubusercontent.com works for file content.
  2. Before bumping, confirm no in-repo task references the removed chain IDs (search src/tasks/ and configs). If a live task still needs a removed chain, escalate instead of bumping.
  3. Update the gitlink:
    • If the submodule can be fetched: git -C lib/superchain-registry fetch && git -C lib/superchain-registry checkout <SHA> && git add lib/superchain-registry
    • If the registry remote is unfetchable but you have the SHA: git update-index --cacheinfo 160000,<SHA>,lib/superchain-registry
  4. Verify only the gitlink changed: git diff --cached --stat should show a single line for lib/superchain-registry.
  5. Commit and open a PR. CI re-runs the check against the newly pinned commit.
Show full SKILL.md (71 more words)Show less

Note on strictness / longer-term fix

The recurring root cause is the check's structural strictness: it hard-fails on any upstream chain removal, even though a removed chain is harmless to superchain-ops. A longer-term option (for maintainers, not part of the routine fix) is to treat "remote missing" as a warning rather than a hard failure, while still hard-failing on address mismatches. Do not implement that as part of a routine drift bump.

© ethereum-optimism, 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 .claude/skills/fix-check-superchain-registry of ethereum-optimism/superchain-ops.

Open the folder on GitHubat commit 7833789

Compare with similar skills

Fix Check Superchain Registry 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.

Fix Check Superchain Registry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix Check Superchain Registry this skillethereum-optimism/superchain-ops99—~932Automated safety check: PassMIT
CI Failure Triage and RepairChachamaru127/claude-code-harness3.2k1 repos~1.1kAutomated safety check: NotesMIT
Reviewwerf/werf4.7k—~2kAutomated safety check: PassApache-2.0
Releasechampionswimmer/pi-context-prune245—~907Automated safety check: PassNone
GitHub Workflow AutomationFNOSP/FlyNarwhal5098 repos~5.4kAutomated safety check: PassAGPL-3.0
GitLab ExplorerWide-Moat/open-computer-use126—~891Automated safety check: PassCustom licence

Similar skills

  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes
  • Review

    werf/werf

    Code review of a pull request, branch, or diff. An agent skill from werf/werf.

    4.7k GitHub stars~2k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Release

    championswimmer/pi-context-prune

    Creates a repository release for this Pi package. An agent skill from championswimmer/pi-context-prune.

    245 GitHub stars~907 tokensUpdated 10 days ago
    DevOps & CloudAuto-check passed
  • Automate GitHub workflows with AI assistance. An agent skill from FNOSP/FlyNarwhal.

    509 GitHub starsUsed in 8 repos~5.4k tokens
    DevOps & CloudAuto-check passed
  • GitLab Explorer

    Wide-Moat/open-computer-use

    Explore GitLab repositories using glab CLI and git commands.

    126 GitHub stars~891 tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed
  • Agr Release

    computerlovetech/agr

    Release process for the agr package. An agent skill from computerlovetech/agr.

    451 GitHub stars~1.6k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

More from ethereum-optimism/superchain-ops

  • Mark Task Executed

    ethereum-optimism/superchain-ops

    Mark one or more superchain-ops tasks as EXECUTED by updating each task README's Status line to link the on-chain execution transaction, then open a PR.

    99 GitHub stars~679 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Fix Check Superchain Registry

What does Fix Check Superchain Registry do?

Diagnose and fix a failing checksuperchainregistry CircleCI job on superchain-ops, typically caused by the pinned lib/superchain-registry submodule drifting from upstream main. Fix Check Superchain Registry is an agent skill from ethereum-optimism/superchain-ops. Diagnose and fix a failing checksuperchainregistry CircleCI job on superchain-ops, typically caused by the pinned lib/superchain-registry submodule drifting from upstream main.

When should I use Fix Check Superchain Registry?

Fix Check Superchain Registry fits situations like: tasks that involve CI/CD.

How do I install Fix Check Superchain Registry in Claude Code?

Run `npx skills add ethereum-optimism/superchain-ops --skill fix-check-superchain-registry -a claude-code`. Or copy the skill folder (.claude/skills/fix-check-superchain-registry in ethereum-optimism/superchain-ops) into .claude/skills/fix-check-superchain-registry in your project. Claude Code loads it when a task matches its description.

How do I install Fix Check Superchain Registry in Codex?

Run `npx skills add ethereum-optimism/superchain-ops --skill fix-check-superchain-registry -a codex`. Or copy the skill folder (.claude/skills/fix-check-superchain-registry in ethereum-optimism/superchain-ops) into .agents/skills/fix-check-superchain-registry in your project. Codex loads it when a task matches its description.

Can I use Fix Check Superchain Registry 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 ethereum-optimism/superchain-ops --skill fix-check-superchain-registry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-check-superchain-registry, .gemini/skills/fix-check-superchain-registry, .github/skills/fix-check-superchain-registry and .opencode/skills/fix-check-superchain-registry in your project.

What does Fix Check Superchain Registry need to run?

Going by SKILL.md and its folder, Fix Check Superchain Registry needs the command-line tools its instructions call (git, curl, jq, just and bash).

Does Fix Check Superchain Registry access the network?

SKILL.md names 2 domains. In commands or code: raw.githubusercontent.com and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Fix Check Superchain Registry 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 Fix Check Superchain Registry use?

Fix Check Superchain Registry 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 Fix Check Superchain Registry use?

About 932 tokens (SKILL.md is roughly 3.7k 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 Fix Check Superchain Registry?

Skills that share tags, products or a category with Fix Check Superchain Registry: CI Failure Triage and Repair (Chachamaru127/claude-code-harness, 3.2k stars), Review (werf/werf, 4.7k stars), Release (championswimmer/pi-context-prune, 245 stars) and GitHub Workflow Automation (FNOSP/FlyNarwhal, 509 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Check Superchain Registry?

ethereum-optimism (a GitHub organization) maintains it in ethereum-optimism/superchain-ops, which has 99 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

Source: ethereum-optimism/superchain-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.