agentleFS
Kali-DecoderKali-Decoder/Midnight-Skills/.agents/skills/midnight-environment-setup/SKILL.md

midnight-environment-setup

Skill18 starsChanged 17 days agoMITView on GitHub

Automatically prepare a complete Midnight development environment — Compact compiler, PATH, Docker, proof server, and VS Code extension. Use before building, compiling, or deploying any Midnight application when tooling is missing. Triggers: "set up Midnight", "install Compact", "proof server", "compact: command not found", "environment setup", "first time Midnight dev".

  • Pipes a download into a shell

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only if a step cannot be completed because of permission limitations, operating system restrictions, missing GUI access, or unavailable …

    line 25
  2. Distinctive:

    Never immediately paste installation documentation.

    line 27
  3. Distinctive:

    If Compact is not installed:

    line 59
  4. Distinctive:

    Wait until installation finishes.

    line 65
  5. Distinctive:

    If Compact still cannot be found, append:

    line 85
  6. Distinctive:

    Always install the latest compiler.

    line 97
  7. Distinctive:

    If Docker is unavailable:

    line 125
  8. Distinctive:

    If port 6300 is occupied, retry using:

    line 149
  9. Distinctive:

    If VS Code exists:

    line 161
  10. Distinctive:

    Ask the user to launch Docker Desktop and wait until the engine is fully started.

    line 213
  11. Distinctive:

    Always prefer automation over explanation.

    line 235
  12. Distinctive:

    Only request manual intervention when automation is impossible due to permission, GUI, or operating system limitations.

    line 237
  13. Distinctive:

    After every automated action, verify success before proceeding.

    line 239
  14. Distinctive:

    Never assume a command succeeded without checking its output.

    line 241

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Midnight Environment Setup

Goal

Automatically prepare a complete Midnight development environment for the user.

This skill should always be executed before attempting to build, compile, or deploy any Midnight application if the required tooling is not already installed.


Responsibilities

The AI assistant should attempt to perform every installation step automatically.

Only if a step cannot be completed because of permission limitations, operating system restrictions, missing GUI access, or unavailable terminal access should the assistant ask the user to complete that specific step manually.

Never immediately paste installation documentation.


Step 1 — Detect Environment

Determine:

  • Operating System
  • Shell (bash/zsh)
  • Docker availability
  • VS Code availability
  • Compact installation
  • Current PATH
  • Existing compiler version

Commands that may be useful:

uname -a
which compact
compact --version
compact compile --version
docker --version
code --version
echo $SHELL

Step 2 — Install Compact

If Compact is not installed:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/midnightntwrk/compact/releases/latest/download/compact-installer.sh | sh

Wait until installation finishes.


Step 3 — Refresh PATH

Determine shell.

If zsh:

source ~/.zshrc

If bash:

source ~/.bashrc

If Compact still cannot be found, append:

export PATH="$HOME/.compact/bin:$PATH"

Reload shell again.


Step 4 — Update Compiler

Always install the latest compiler.

compact update

Step 5 — Verify Installation

Run

compact --version

compact compile --version

which compact

Installation is considered successful only if all commands execute without errors.


Step 6 — Docker

Check Docker availability.

If Docker is unavailable:

Explain that Docker Desktop must be installed manually.

https://www.docker.com/products/docker-desktop/

Pause until Docker is running.


Step 7 — Start Proof Server

Run

docker run -p 6300:6300 midnightntwrk/proof-server:latest midnight-proof-server -v

Verify logs indicate:

Listening on http://localhost:6300

If port 6300 is occupied, retry using:

docker run -p 6301:6300 midnightntwrk/proof-server:latest midnight-proof-server -v

Inform the user that applications must now use port 6301.


Step 8 — VS Code Extension

If VS Code exists:

Guide the user to install the Compact VS Code extension (VSIX package).

AI agents cannot reliably install VS Code extensions through GUI interactions unless the environment explicitly supports it.

Provide concise instructions:

  1. Download the Compact VSIX package.
  2. Open VS Code.
  3. Extensions.
  4. Install from VSIX.
  5. Select the downloaded file.

Final Verification Checklist

Confirm:

  • Compact installed
  • Latest compiler installed
  • PATH configured
  • Docker running
  • Proof Server running
  • VS Code extension installed (or user informed)

Troubleshooting

compact: command not found

Reload shell.

If needed:

export PATH="$HOME/.compact/bin:$PATH"
source ~/.zshrc

or

source ~/.bashrc

Docker not running

Ask the user to launch Docker Desktop and wait until the engine is fully started.


Port 6300 already in use

Use:

docker run -p 6301:6300 midnightntwrk/proof-server:latest midnight-proof-server -v

and configure applications to use:

http://localhost:6301

Agent Behavior

Always prefer automation over explanation.

Only request manual intervention when automation is impossible due to permission, GUI, or operating system limitations.

After every automated action, verify success before proceeding.

Never assume a command succeeded without checking its output.

The goal is to leave the user with a fully working Midnight development environment ready to build, compile, and deploy DApps.

Author: Kali-Decoder

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.