A collection of AI agent skills for working with the Blockscout ecosystem — blockchain explorers, APIs, and supporting services.

Each skill is a self-contained directory of structured instructions and helper scripts that give an AI agent domain expertise in a specific area. Skills follow the markdown-based format compatible with Claude Code, Codex, Cursor, OpenClaw, Claude Cowork, and other agents that support skill/instruction loading.

Different skills depend on different Blockscout backends. Pick the row that matches the skill you want to install:

Each skill is a directory with a SKILL.md entry point and supporting docs/scripts. Integration depends on your agent platform — see examples below. In the snippets below, replace <skill> with the directory name of the skill you want to install (e.g. blockscout-analysis, web3-dev).

One command installs a skill to 40+ coding agents (Claude Code, Codex, Cursor, Cline, Copilot, Windsurf, Continue, and more):

npx skills@latest add https://github.com/blockscout/agent-skills --skill <skill>

Use -g to install globally, or -a <agent> to target a specific agent. See skills.sh/docs for the full list of supported agents and options.

Note: The Skills CLI installs the skill instructions only. Skill-specific backends (MCP server for blockscout-analysis, PRO API key for web3-dev) are not configured automatically — see Prerequisites.

For blockscout-analysis, no separate MCP server configuration is needed — it is set up automatically as part of the plugin installation. For web3-dev, you still need to provide a PRO API key (see Prerequisites).

claude plugin marketplace add blockscout/agent-skills
claude plugin install <plugin>@blockscout-ai

Replace <plugin> with blockscout-analysis or web3-dev (or run the install command once per plugin).

Must be configured separately for Chat/Cowork and for Code by the same procedure.

1. Choose Customize in the sidebar:

   

2. Choose Browse plugins → Personal → Add marketplace from GitHub:

   

3. Enter the GitHub repo ID blockscout/agent-skills and press Sync:

   

4. The marketplace blockscout-ai will appear in the list of Personal plugins. Click Install on each skill plugin you want (blockscout-analysis, web3-dev):

   

5. Once installed, the plugin details are available in the Customize window:

   

6. If the plugin has MCP servers associated (e.g. blockscout-analysis), their info will be available in the Connectors sub-item:

   

Add the marketplace first, then enable the skill plugin from inside Codex via the /plugin slash command (the command opens an interactive picker). For blockscout-analysis, the Blockscout MCP server is auto-configured by the plugin — no manual MCP setup required. For web3-dev, provide a PRO API key (see Prerequisites).

codex plugin marketplace add blockscout/agent-skills

Then run codex and type:

/plugin

Select the marketplace blockscout-ai and enable the plugin(s) you want (blockscout-analysis, web3-dev).`

The first command (registering the Blockscout MCP server) is only needed for blockscout-analysis; skip it for web3-dev.

gemini mcp add --transport http blockscout https://mcp.blockscout.com/mcp   # blockscout-analysis only
gemini skills install https://github.com/blockscout/agent-skills --path <skill>

The skills and the underlying Blockscout infrastructure are under continuous development. Update the marketplace/plugin (Claude) or re-install the skill (Gemini, Codex) periodically to pick up the most recent versions.

To create a distributable zip of a skill:

bash tools/package.sh <skill-directory>

This produces <skill-directory>-<version>.zip and <skill-directory>-<version>.skill (version read from SKILL.md frontmatter) containing all tracked files except .gitignore and README.md. The .skill file is identical to the .zip but uses the extension recognised by Claude Desktop and Gemini CLI for one-click import.

The Codex marketplace requires plugins to be self-contained directory trees with no symlinks. To keep each skill as a single source-of-truth directory at the repo root while still serving Codex, the published Codex layout lives on a dedicated codex-plugins branch. To regenerate that branch from the current main (or a release tag) and push it:

bash tools/publish-codex-plugins.sh [<source-ref>] [<target-branch>]

Defaults are main and codex-plugins. The script reads only committed content from <source-ref>, dereferences the symlinks under .agents/plugins/*/skills/ into real directories, copies .agents/plugins/marketplace.json verbatim, writes a short README.md, and pushes the result. See .memory_bank/specs/publish-codex-plugins-spec.md for the full specification.

MIT