debugging-moonbeam

Diagnose Moonbeam parachain issues with reproducible debugging workflows.

3|2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Moonsong-Labs/knowledge-work-plugins --skill debugging-moonbeam-moonsong-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-moonbeam
Source: https://github.com/Moonsong-Labs/knowledge-work-plugins/tree/main/moonbeam-engineering/skills/debugging-moonbeam
Command: npx skills add https://github.com/Moonsong-Labs/knowledge-work-plugins --skill debugging-moonbeam-moonsong-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugs issues in the Moonbeam parachain including runtime panics, EVM execution failures, XCM message delivery problems, and client-side errors. Use when encountering transaction failures, unexpected behavior, state inconsistencies, block production issues, or RPC errors.

Core Features & Use Cases

  • Lazy-loading workflows to reproduce production-like states using a local node.
  • Detailed runtime, EVM, XCM, and RPC debugging workflows with practical guidance.
  • Investigation and tooling coverage for common failure modes such as panics, trace failures, and state mismatches.

Quick Start

Start a local Moonbeam dev node with verbose logging and follow the debugging workflow to reproduce and fix issues.

Frequently Asked Questions about debugging-moonbeam

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Moonbeam parachain runtime panics and EVM execution failures?

To debug Moonbeam parachain runtime panics and EVM execution failures, use guided debugging workflows that require access to runtime logs, tracing tooling, and configurable Moonbeam builds to reproduce and verify fixes locally.

What is the best way to diagnose XCM message delivery problems on a Moonbeam node?

Diagnosing XCM message delivery problems on a Moonbeam node involves following detailed XCM debugging workflows using runtime logs and tracing tooling to investigate failures across development, test, and production environments.

How do I reproduce Moonbeam production state issues locally for safe debugging?

You can reproduce Moonbeam production state issues locally by using lazy-loading workflows to recreate production-like states on a local node with verbose logging enabled for safe investigation.

Does debugging Moonbeam RPC failures and block production anomalies require a specific node configuration?

Debugging Moonbeam RPC failures and block production anomalies requires configurable Moonbeam builds with access to runtime logs and tracing tooling to investigate block-production anomalies and client-side errors.

When should I use specialized tracing workflows for Moonbeam state inconsistencies instead of general EVM debugging?

Use specialized tracing workflows for Moonbeam state inconsistencies when encountering unexpected behavior or trace failures that standard EVM debugging cannot resolve, applying detailed runtime and state mismatch investigation techniques.