midnight-tooling:midnight-debugging

Diagnose Midnight development toolchain errors with structured checks and remediation commands.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/aaronbassett/midnight-knowledgebase --skill midnight-tooling-midnight-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: midnight-tooling:midnight-debugging
Source: https://github.com/aaronbassett/midnight-knowledgebase/tree/main/plugins/midnight-tooling/skills/midnight-debugging
Command: npx skills add https://github.com/aaronbassett/midnight-knowledgebase --skill midnight-tooling-midnight-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers quickly diagnose and resolve common Midnight toolchain errors that block progress, from PATH and version mismatches to node import issues, proof server failures, and compilation problems.

Core Features & Use Cases

  • Structured diagnostics: follows a step-by-step workflow using the built-in doctor, version checks, and error guides to identify root causes.
  • Targeted remediation: provides concrete steps and commands to fix common issues and verify outcomes.
  • Use case: when a Midnight project stalls due to a cryptic error like ERR_UNSUPPORTED_DIR_IMPORT, use this skill to run environment diagnostics, apply fixes, and confirm operation with /midnight:check.

Quick Start

Run the debugging skill to automatically diagnose your Midnight environment and guide you toward fixes.

Frequently Asked Questions about midnight-tooling:midnight-debugging

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

FAQPage Schema
How do I fix Midnight toolchain errors like ERR_UNSUPPORTED_DIR_IMPORT?

Fix Midnight toolchain errors by running a structured diagnostic workflow that checks PATH, version, Node import, proof server, and compilation issues. Use local scripts like diagnose-environment.py to identify root causes and apply targeted remediation commands to resolve the failure.

Why does my Midnight development environment fail version checks?

Midnight version checks fail due to PATH mismatches or incorrect toolchain versions. Run the built-in doctor command and environment diagnostics to detect version conflicts, then follow the step-by-step remediation strategies to align your setup and confirm operation with /midnight:check.

What's the best way to diagnose Midnight proof server failures?

Diagnose Midnight proof server failures by following a structured diagnostic workflow using the built-in doctor and error-resolution guides. Run environment diagnostics to isolate the failure, apply the recommended commands, and verify the proof server operates correctly.

Can I resolve Midnight Node import issues without manual troubleshooting?

Resolve Midnight Node import issues automatically by running the debugging skill to execute environment diagnostics. It guides you through step-by-step checks for Node import problems, provides concrete remediation commands, and validates fixes using the /midnight:check command.

What should I do when Midnight compilation problems block my project?

When Midnight compilation problems block your project, run the diagnostic workflow to identify compilation issues. Use the error-resolution guides and diagnose-environment.py script to pinpoint the root cause, apply the provided fixes, and verify successful compilation.

Does the Midnight diagnostic workflow check PATH and environment setup?

The Midnight diagnostic workflow checks PATH and environment setup using the built-in doctor command and diagnose-environment.py script. It validates your toolchain configuration, identifies mismatches, and provides concrete steps to remediate environment issues fast.