midnight-tooling:devnet

Resolve latest stable Midnight devnet component images and generate devnet.yml.

37|9|Updated Feb 25, 2026

Search Tags:#automation #docker #devnet #version-resolution #midnight-tooling #devnet-management

Ready to run

npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-tooling-devnet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: midnight-tooling:devnet
Source: https://github.com/devrelaicom/midnight-expert/tree/main/plugins/midnight-tooling/skills/devnet
Command: npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-tooling-devnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinate and manage the Midnight local development network (devnet) lifecycle, including generating configuration, resolving image versions, and starting/stopping services.

Core Features & Use Cases

Resolve latest stable image versions for node, indexer, and proof server, then generate a ready-to-run devnet.yml.
Start, stop, and monitor the 3-service devnet (node, indexer, proof-server) with health checks and lifecycle commands.
Read endpoints and configuration to connect DApps and wallets to the local network.
Use cases: quickly spin up a reproducible test environment for smart contracts and tooling.

Quick Start

Run /midnight-tooling:devnet start to generate the devnet.yml, pull latest images, and launch the local devnet.

Frequently Asked Questions about midnight-tooling:devnet

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

FAQPage Schema

How do I set up a local Midnight devnet for smart contract testing?▼

You set up a local Midnight devnet by generating a ready-to-run devnet.yml that resolves the latest stable images for the node, indexer, and proof-server. This creates a reproducible local environment for testing smart contracts and connecting DApps.

How does version resolution work for Midnight devnet components?▼

Version resolution for Midnight devnet components works by automatically identifying and pulling the latest stable Docker images for the node, indexer, and proof-server. This ensures your local devnet environment remains reproducible and up-to-date across lifecycle operations.

Do I need Docker and jq installed to manage a Midnight devnet?▼

Yes, you need Docker to run the containerized services and jq to process JSON data during devnet management. These dependencies are required to execute the scripts that resolve image versions and orchestrate the node, indexer, and proof-server lifecycle.

Can I manage the start, stop, and status checks for a Midnight devnet?▼

Yes, you can manage the start, stop, and status checks for a Midnight devnet using lifecycle orchestration commands. The devnet management tool applies health checks to monitor the 3-service devnet, ensuring the node, indexer, and proof-server are running correctly.

How do I connect my DApp to a local Midnight devnet?▼

To connect your DApp to a local Midnight devnet, you read the exposed endpoints and configuration from the running devnet. This allows your DApps and wallets to interface directly with the local Midnight network for testing and development.

What are the limitations of using a local devnet for Midnight development?▼

A local Midnight devnet is designed specifically as a reproducible test environment for smart contracts and tooling, meaning it is not optimized for production scale. Lifecycle management is limited to generating configurations and orchestrating the start and stop of the 3-service local network.