ワンクリックで
investigate
// Debug Ethereum devnet or network issues. Use when diagnosing finality delays, network splits, offline nodes, client bugs, or general network health problems. Works for both local Kurtosis devnets and remote hosted deployments.
// Debug Ethereum devnet or network issues. Use when diagnosing finality delays, network splits, offline nodes, client bugs, or general network health problems. Works for both local Kurtosis devnets and remote hosted deployments.
Query Ethereum network data via ethpandaops CLI or MCP server. Use when analyzing blockchain data, block timing, attestations, validator performance, network health, or infrastructure metrics. Provides access to ClickHouse (blockchain data), Prometheus (metrics), Loki (logs), and Dora (explorer APIs).
Run schema probing self-play loop to find and fix ClickHouse schema ambiguity in the panda repo. Use when the user wants to improve query reliability by finding where the agent picks different tables for the same question.
Install panda as an MCP server in AI coding assistants (Claude Code, Claude Desktop, Cursor). Use when setting up panda, configuring MCP, or connecting AI tools to panda. Triggers on: install mcp, setup mcp, configure mcp, register mcp, add mcp server.
Install and set up panda from scratch. Use when the user wants to install panda, get started with panda, or set up their environment. Triggers on: install panda, setup panda, get started, getting started.
Add a new datasource module to ethpandaops/panda. Triggers on: add module, new module, create module, add plugin, new plugin, create plugin, add datasource.
Extract a reusable runbook from a successful investigation or troubleshooting session. Use after completing a multi-step diagnosis that could help future investigations.
| name | investigate |
| description | Debug Ethereum devnet or network issues. Use when diagnosing finality delays, network splits, offline nodes, client bugs, or general network health problems. Works for both local Kurtosis devnets and remote hosted deployments. |
| argument-hint | <network-name and/or issue description> |
| user-invocable | false |
This skill routes to the appropriate debugging runbook based on whether the target is a local Kurtosis devnet or a remote hosted deployment.
The user MUST specify which network to debug. If not provided, ask them.
Run both checks in parallel:
# Check for local Kurtosis enclaves
kurtosis enclave ls 2>/dev/null
# Check for remote datasources via panda
panda datasources --json 2>/dev/null
If the target network matches a Kurtosis enclave name → local devnet. Load the local debugging procedure:
panda search runbooks "debug local devnet"
Then follow that runbook. It covers Kurtosis service discovery, local Dora/Loki detection (localhost:3100), direct CL/EL API queries, Kurtosis-specific Loki label schema, and kurtosis service logs fallback.
If the target network is found in panda datasources (Dora networks, Loki instances) → remote deployment. Load the remote debugging procedure:
panda search runbooks "debug devnet"
Then follow that runbook. It covers remote datasource discovery, Dora data collection, remote Loki log investigation, and ethnode RPC validation.
If found in neither → stop, tell the user the network was not found in any local enclave or remote datasource.
panda search examples for query patterns — search before writing complex queries from scratch./workspace/ — provide the path to the user at the end.