ワンクリックでManusで任意のスキルを実行

blockscout

スター1

フォーク0

更新日2026年7月14日 16:04

Blockscout MCP tool reference for on-chain data queries. Covers all 16 tools: address info, transactions, token transfers, NFTs, contract ABI/source, read-only calls, ENS resolution, and block data across 8+ chains. TRIGGER when: user asks about on-chain data, contract state, token balances, transaction history, ENS lookup, NFT holdings, or uses blockscout MCP tools. DO NOT TRIGGER when: user asks about crypto market prices or trading volume (use coingecko skill), or writing Solidity code (use solidity-auditor skill).

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

DROOdotFOO

DROOdotFOO/agent-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Blockscout MCP

On-chain data queries via Blockscout MCP server (already configured). 16 tools across address intelligence, transactions, contracts, and blocks.

Chain support

EVM-only. Blockscout covers 90+ EVM chains. Not available for native Solana or Tron -- use CoinGecko contract endpoints for token data on those chains.

Solana via Neon EVM: Chain 245022934 covers the Neon EVM layer on Solana (EVM-compatible contracts deployed on Solana).

Common chain IDs

Chain	ID	Chain	ID
Ethereum	1	Arbitrum One	42161
Polygon	137	OP Mainnet	10
Base	8453	zkSync Era	324
Gnosis	100	Scroll	534352
Celo	42220	Mode	34443
Neon EVM (Solana)	245022934	Filecoin	314
Robinhood Chain	4663

Robinhood Chain (4663) is an Arbitrum Orbit L3 (native currency ETH), reachable by chain_id like any other -- no instance URL needed.

Default: Ethereum (1). Use get_chains_list to discover all 90+ supported chains.

Discover a chain ID

For any chain not in the table -- Orbit L3s, new rollups, or chains with their own Blockscout instance (e.g. robinhoodchain.blockscout.com) -- pass a name substring to get_chains_list instead of assuming it is unsupported:

get_chains_list(query="robinhood")
  -> { name: "Robinhood Chain", chain_id: "4663", ecosystem: "Arbitrum Orbit" }

If a chain has a Blockscout explorer, it is almost certainly reachable through the MCP by chain_id -- you do not need the instance URL.

Reference

File	Topic
tools-reference.md	All 16 tools grouped by category
usage-patterns.md	Common workflows, pagination, error handling

What You Get

Reference documentation for all 16 Blockscout MCP tools covering address intelligence, transactions, contracts, and block data.
Chain ID lookup tables and common usage patterns for querying on-chain state across 90+ EVM chains.
Pagination handling, error recovery, and time-based query guidance for efficient data retrieval.

Read Fluidify Regen incidents and extract the join keys needed to pivot from an incident into its underlying OTel telemetry. Regen is a self-hosted incident / on-call tool with a REST API but no MCP server; this agent makes incidents first-class and emits a ready-to-run SigNoz filter hint -- the incident side of the incident <-> telemetry loop (SigNoz is the telemetry side). TRIGGER when: user asks about Regen incidents, on-call/paging state, "what's on fire", incident triage, ack/resolve an incident, or invokes "/regen"; or wants the service.name + labels + time window to feed into SigNoz. DO NOT TRIGGER when: user is working on the regen agent code itself; or wants to query the telemetry directly (use the signoz skill -- regen hands off to it).

2026-07-141

signoz

DROOdotFOO/agent-skills

SigNoz MCP tool reference for querying a live observability backend (OTel metrics, traces, logs) plus alerts, dashboards, saved views, and notification channels. Covers all ~41 signoz_* tools, the 4 built-in MCP prompts, the resource-attribute-first filtering rule, and the regen incident -> SigNoz correlation loop on the mini-axol/Riddler deployment. TRIGGER when: user asks to query SigNoz, inspect a service's errors/latency, search OTel logs or traces, read/aggregate metrics, triage an alert, or uses signoz_* MCP tools; or pivots from a regen incident into telemetry. DO NOT TRIGGER when: user wants to DESIGN SLOs/alerts/dashboards conceptually (use observability-designer skill), or READ/ack/resolve incidents in Regen itself (use the regen agent/skill -- signoz is the telemetry side of that loop).

2026-07-141

sentinel

DROOdotFOO/agent-skills

Monitor on-chain contracts for anomalous transactions. Checks for large transfers, ownership changes, unusual methods, and selfdestruct calls via Blockscout API v2. TRIGGER when: user asks about contract monitoring, "check this contract", on-chain alerts, "any suspicious transactions", or invokes "/sentinel". DO NOT TRIGGER when: user is working on sentinel agent code itself.

2026-07-141

raxol-payments

DROOdotFOO/agent-skills

Agentic commerce for Raxol agents in Elixir: the raxol_payments + raxol_acp packages (Xochi/Riddler/MPP/Permit2/x402 protocols, agent wallets, spend limits, stealth + privacy tiers, ZKSAR trust scores, and the ACP job lifecycle). TRIGGER when: mix.exs lists :raxol_payments or :raxol_acp; code imports Raxol.Payments.* or Raxol.ACP.*; user asks about agent wallets, HTTP 402 auto-pay, Xochi/Riddler cross-chain transfers, stealth addresses / privacy tiers, ZKSAR attestations, spend gating, or the ACP (Agent Commerce Protocol) job state machine / offerings. DO NOT TRIGGER when: writing or auditing Solidity contracts (use solidity-auditor skill); general Ethereum tooling / RPC / explorer questions (use ethskills skill); ZK circuit design in Noir (use noir skill); the core Raxol agent/TUI framework (use raxol skill); the Symphony orchestrator (use raxol-symphony skill).

2026-07-131

raxol

DROOdotFOO/agent-skills

Raxol terminal framework for TUI apps and AI agents in Elixir (v2.6, 15-package monorepo). TRIGGER when: code imports Raxol modules (Raxol.Agent, Raxol.Core, Raxol.MCP, Raxol.LiveView, Raxol.Workflow, Raxol.Headless), mix.exs lists :raxol / :raxol_agent / :raxol_core / :raxol_mcp as a dependency, user asks about building TUI apps or AI agents with Raxol, agent memory/self-improvement, the workflow engine, or Raxol headless/MCP tools. DO NOT TRIGGER when: general Elixir patterns (use droo-stack skill), Claude API / Anthropic SDK usage (use claude-api skill), agentic commerce / payments / ACP job sessions (use raxol-payments skill), the Symphony coding-agent orchestrator (use raxol-symphony skill), or other TUI frameworks (Scenic, Termbox, etc.).

2026-07-131

raxol-symphony

DROOdotFOO/agent-skills

Symphony: the Raxol tracker-driven coding-agent orchestrator (raxol_symphony, pre-alpha). Turns tracker issues into autonomous agent runs in isolated workspaces, surfaces evidence (CI/PR/asciinema), and supports human-in-the-loop paused runs across six surfaces. TRIGGER when: mix.exs lists :raxol_symphony; code imports Raxol.Symphony.*; there is a WORKFLOW.md driving an orchestrator; user asks about tracker-driven agent orchestration, Symphony runners (RaxolAgent/Codex), evidence capture, or paused-run resume with Raxol. DO NOT TRIGGER when: building a single Raxol agent or the core framework (use raxol skill); agent payments / ACP job sessions (use raxol-payments skill); generic multi-agent system design without Symphony (use agent-designer skill); the Claude Agent SDK (use claude-api).

2026-07-131

name	blockscout
description	Blockscout MCP tool reference for on-chain data queries. Covers all 16 tools: address info, transactions, token transfers, NFTs, contract ABI/source, read-only calls, ENS resolution, and block data across 8+ chains. TRIGGER when: user asks about on-chain data, contract state, token balances, transaction history, ENS lookup, NFT holdings, or uses blockscout MCP tools. DO NOT TRIGGER when: user asks about crypto market prices or trading volume (use coingecko skill), or writing Solidity code (use solidity-auditor skill).
metadata	{"author":"DROOdotFOO","version":"1.1.0","tags":"blockscout, blockchain, onchain, mcp, ethereum, web3"}

Blockscout MCP

On-chain data queries via Blockscout MCP server (already configured). 16 tools across address intelligence, transactions, contracts, and blocks.

Chain support

EVM-only. Blockscout covers 90+ EVM chains. Not available for native Solana or Tron -- use CoinGecko contract endpoints for token data on those chains.

Solana via Neon EVM: Chain 245022934 covers the Neon EVM layer on Solana (EVM-compatible contracts deployed on Solana).

Common chain IDs

Chain	ID	Chain	ID
Ethereum	1	Arbitrum One	42161
Polygon	137	OP Mainnet	10
Base	8453	zkSync Era	324
Gnosis	100	Scroll	534352
Celo	42220	Mode	34443
Neon EVM (Solana)	245022934	Filecoin	314
Robinhood Chain	4663

Robinhood Chain (4663) is an Arbitrum Orbit L3 (native currency ETH), reachable by chain_id like any other -- no instance URL needed.

Default: Ethereum (1). Use get_chains_list to discover all 90+ supported chains.

Discover a chain ID

get_chains_list(query="robinhood")
  -> { name: "Robinhood Chain", chain_id: "4663", ecosystem: "Arbitrum Orbit" }

If a chain has a Blockscout explorer, it is almost certainly reachable through the MCP by chain_id -- you do not need the instance URL.

Reference

File	Topic
tools-reference.md	All 16 tools grouped by category
usage-patterns.md	Common workflows, pagination, error handling

What You Get

Reference documentation for all 16 Blockscout MCP tools covering address intelligence, transactions, contracts, and block data.
Chain ID lookup tables and common usage patterns for querying on-chain state across 90+ EVM chains.
Pagination handling, error recovery, and time-based query guidance for efficient data retrieval.

blockscout

Blockscout MCP

Chain support

Common chain IDs

Discover a chain ID

Reference

What You Get

See also

Blockscout MCP

Chain support

Common chain IDs

Discover a chain ID

Reference

What You Get

See also

blockscout

Blockscout MCP

Chain support

Common chain IDs

Discover a chain ID

Reference

What You Get

See also

このリポジトリの他の Skills

Blockscout MCP

Chain support

Common chain IDs

Discover a chain ID

Reference

What You Get

See also

このリポジトリの他の Skills