Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From midnight-tooling
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.
npx claudepluginhub devrelaicom/midnight-expert --plugin midnight-toolingHow this skill is triggered — by the user, by Claude, or both
Slash command
/midnight-tooling:troubleshootingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematic diagnosis and resolution of common issues encountered when developing with Midnight Network tools.
references/bun-setup.mdreferences/checking-release-notes.mdreferences/compact-cli-issues.mdreferences/devnet-issues.mdreferences/environment-tooling.mdreferences/environment-urls.mdreferences/err-unsupported-dir-import.mdreferences/nixos-installation.mdreferences/proof-server-issues.mdreferences/searching-issues.mdreferences/version-mismatch.mdreferences/windows-setup.mdThis 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 to "check my setup", "run diagnostics", "doctor", "health check", "verify my installation", "are my plugins working", "check plugin status", "what's broken", "fix my setup", "debug my environment", "check dependencies", "environment check", "troubleshoot setup", or invokes /midnight-expert:doctor. Provides comprehensive health reporting for the midnight-expert ecosystem — plugin installation, MCP servers, external tools, cross-plugin references, and NPM registry.
This skill should be used when the user asks about the Midnight.js SDK, midnight-js packages, @midnight-ntwrk npm packages, setting up SDK providers, deploying or finding contracts with deployContract or findDeployedContract, calling circuits with callTx or submitCallTx, the transaction lifecycle, SDK provider types (WalletProvider, MidnightProvider, PublicDataProvider, ProofProvider, ZkConfigProvider, PrivateStateProvider), testkit-js testing, observable state subscriptions, contract maintenance and verifier keys, or connecting to the indexer or proof server.
Share bugs, ideas, or general feedback.
Systematic diagnosis and resolution of common issues encountered when developing with Midnight Network tools.
Follow this diagnostic sequence for any issue:
| Symptom / Keyword | Reference File |
|---|---|
| NixOS, Nix, nix-shell | references/nixos-installation.md |
| Version mismatch, incompatible versions, compatibility matrix | references/version-mismatch.md |
| ERR_UNSUPPORTED_DIR_IMPORT, stale terminal, node version | references/err-unsupported-dir-import.md |
| Bun, bun runtime, bun setup | references/bun-setup.md |
| Windows, WSL, PowerShell | references/windows-setup.md |
| Wrong URL, incorrect endpoint, wrong network, wrong environment, preprod, testnet, mainnet | references/environment-urls.md |
Proof server, Docker, ZK parameters, port 6300, container (for proof-server-in-devnet issues also check references/devnet-issues.md) | references/proof-server-issues.md |
| compact: command not found, shebang, exec format error, compactc wrapper | references/compact-cli-issues.md |
| direnv, mise, dotenv-cli, COMPACT_DIRECTORY, stale cache | references/environment-tooling.md |
| Devnet, local network, node, indexer, network start | references/devnet-issues.md |
| Wallet initialization, funding, balance, transfers, dust registration | Use the midnight-wallet plugin |
| MCP server not connecting, midnight-devnet MCP error, npx failed | references/devnet-issues.md |
For cross-cutting diagnostic techniques (not tied to a specific symptom):
| Technique | Reference File |
|---|---|
| Search open GitHub issues in midnightntwrk org | references/searching-issues.md |
| Check release notes for known bugs or breaking changes | references/checking-release-notes.md |
Several references instruct fetching the latest documentation from the midnightntwrk/midnight-docs GitHub repository via the octocode MCP tools. This ensures guidance reflects the current state of the docs rather than stale cached knowledge.
Standard fetch pattern using octocode:
githubGetFileContent(
owner: "midnightntwrk",
repo: "midnight-docs",
path: "<path-to-mdx-file>",
fullContent: true
)
When parsing fetched MDX content:
--- delimiters)import ... from ...)<Tabs>, <TabItem>, <Admonition>, etc.) but preserve their text contentMany issues benefit from multiple references. For example, a version mismatch may require:
references/version-mismatch.md - diagnose and fix the mismatchreferences/searching-issues.md - check if others report the same combinationreferences/checking-release-notes.md - verify whether a newer version resolves itWhen a problem is ambiguous, start with references/searching-issues.md to see if the exact error message appears in open issues before diving into specific references.
If the user's issue does not match any row in the routing tables above:
references/searching-issues.md to search for the exact error messagereferences/checking-release-notes.md for recent breaking changesSome references link to other skills in this plugin:
references/checking-release-notes.md depends on the release-notes skill and its references/component-map.md for component directory mappings.references/compact-cli-issues.md references the compact-cli skill's references/installation.md for additional installation detail.references/environment-tooling.md references the compact-cli skill's references/custom-directories.md for per-project toolchain setup.references/devnet-issues.md depends on the devnet skill and its references for network lifecycle details.references/proof-server-issues.md references the proof-server skill for API endpoint details, Docker setup, and version management.