midnight-tooling

Manage a local Midnight devnet — generate compose files, start/stop the network, check status and health, view logs and configuration

Comprehensive diagnostic and health report for the Compact CLI installation, compiler versions, PATH configuration, custom directory setup, proof server status, and plugin dependencies

Install, update, or configure the Compact CLI tool. Supports global installation and per-project configuration with automatic environment setup.

Install, update, or uninstall the Midnight statusline script. Displays proof server and Compact CLI status in the Claude Code status bar.

View Midnight component release notes from the official documentation

This skill should be used when the user asks about the Compact CLI, Compact Dev Tool, Compact Developer CLI, or compact devtools for Midnight Network smart contract development, including setting up the Compact toolchain on a new machine, resolving "compact: command not found" or "No default compiler set" errors, validating that Compact source code compiles correctly, switching between compiler versions, pinning a project to a specific compiler version, understanding why compilation is slow or how to speed it up, figuring out which version of the compiler or language they're running, setting up a project-local toolchain directory, configuring import search paths for multi-file contracts, understanding error messages or exit codes from the compiler or formatter, setting up or uninstalling the Compact toolchain, resolving GitHub API rate limiting when listing or updating versions, or troubleshooting why format or fixup is reporting failures

This skill should be used when the user asks about the Midnight local development network, including "start the devnet", "stop the devnet", "restart the network", "local development network", "midnight node", "midnight indexer", "network status", "network health", "devnet config", "network endpoints", "port 9944", "port 8088", "port 6300", "Docker Compose", "devnet not starting", "local blockchain", "devnet logs", "network ID", "generate devnet", "devnet versions", "update devnet", "devnet stale", "proof server", "devnet volumes", "clean slate", "docker containers", "devnet compose file", "devnet endpoints"

This skill should be used when the user asks about the Midnight proof server in any context — local, testnet, or mainnet. Includes "start the proof server", "restart the proof server", "stop the proof server", "proof server not working", "proof server logs", "check if proof server is running", "proof server port 6300", "proof server version", "proof server image tag", "proof server health check", "proof server API endpoints", "Docker container for proofs", "set up Docker for the proof server", or "proof server endpoint". Covers proof server concepts, version selection, API endpoints, standalone Docker usage, and troubleshooting. For local development setup, see the devnet skill.

This skill should be used when the user asks about "Midnight release notes", "what changed in version X", "latest release", "changelog", "show me the changelog", "what's new in Midnight", "component versions", "list versions", "compact release notes", "ledger release notes", "wallet release notes", "proof server release notes", "node release notes", "lace release notes", "midnight-js release notes", "indexer release notes", "breaking changes", "latest version of X", viewing release history, checking component update details, or comparing versions of any Midnight Network component.

This skill should be used when the user encounters errors, installation failures, version mismatches, or unexpected behavior with Midnight Network tools. Covers Node.js import errors, Compact CLI issues, proof server and Docker problems, devnet startup failures, environment and URL misconfiguration, NixOS and Windows/WSL setup, and searching Midnight GitHub issues for known bugs. For wallet initialization or funding failures, use the midnight-wallet plugin.