How do I install the Nts Wsl Integration skill?

Run npx skillmds@latest add tomevault-io/nts-wsl-integration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Nts Wsl Integration safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nts Wsl Integration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nts Wsl Integration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nts Wsl Integration?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nts Wsl Integration by tomevault-io

Name: Nts Wsl Integration
Author: tomevault-io

Nts Wsl Integration

Set up and verify the NTS integration test environment in WSL. Use when Codex is asked to run, fix, or document NTS.Tests.Integration in WSL; install or repair Azure Functions Core Tools for this repo; create a WSL func shim; use Docker Desktop from WSL; start Azurite; or diagnose integration harness startup failures involving func, Docker, Azurite, MongoDB connection strings, or WSL localhost. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

NTS WSL Integration

Core Rule

Read the repository AGENTS.md before making changes. If it forbids writes outside the working directory, ask the user to lift that rule before creating ~/.local/bin/func or editing ~/.bashrc.

Use The Linux Func Path

Prefer Linux Azure Functions Core Tools under the repository .tools/ directory. Do not rely on Windows func.exe for the integration harness: it can start the Functions host, but WSL may not reach the Windows loopback listener at 127.0.0.1:<port>.

Use Docker Desktop's WSL CLI whenever Docker is needed:

/mnt/wsl/docker-desktop/cli-tools/usr/bin/docker

Setup Workflow

From the repository root:

Verify the repo rules:

sed -n '1,180p' AGENTS.md

If home-directory writes are allowed or the user explicitly lifts the rule, run the setup script:

bash .codex/skills/nts-wsl-integration/scripts/setup_wsl_integration.sh

If home-directory writes are not allowed yet, install only repo-local tools first:

bash .codex/skills/nts-wsl-integration/scripts/setup_wsl_integration.sh --skip-shim --skip-bashrc

Verify without modifying files:

bash .codex/skills/nts-wsl-integration/scripts/setup_wsl_integration.sh --verify-only

Run the integration project with the expected output levels:

PATH="/mnt/wsl/docker-desktop/cli-tools/usr/bin:$HOME/.local/bin:$PATH" dotnet build tests/NTS.Tests.Integration/NTS.Tests.Integration.csproj -v:q
PATH="/mnt/wsl/docker-desktop/cli-tools/usr/bin:$HOME/.local/bin:$PATH" dotnet test tests/NTS.Tests.Integration/NTS.Tests.Integration.csproj -v:m

Expected Installed Pieces

.tools/node: local Linux Node runtime used for npm/extraction.
.tools/npm: local npm prefix containing azure-functions-core-tools.
.tools/npm/node_modules/azure-functions-core-tools/bin/func: Linux func binary.
~/.local/bin/func: optional shim pointing at the repository-local Linux func.
~/.bashrc: optional PATH line placing Docker Desktop's WSL CLI and ~/.local/bin first.

.tools/ is local machine state and should stay git-ignored.

Common Failures

func: command not found: create or repair the shim after user approval for home-directory writes.
Docker reports client version 1.43 is too old: use /mnt/wsl/docker-desktop/cli-tools/usr/bin/docker instead of /usr/bin/docker.
MongoDB connection string is null: usually caused by launching Windows func.exe; switch to Linux func.
Nexus HTTP did not become healthy while Functions lists routes: often Windows func.exe loopback isolation; switch to Linux func.
Azurite storage errors: start the azurite Docker container on ports 10000, 10001, and 10002.

Script Notes

The setup script downloads a large Functions Core Tools zip from Microsoft's CDN and extracts about 1.3 GB under .tools/. This can be slow on /mnt/* drives. Prefer checking whether .tools/npm/node_modules/azure-functions-core-tools/bin/func --version works before repeating the download.

Source: Not-Endurance/not-timing-system — distributed by TomeVault.

---name: nts-wsl-integrationdescription: Set up and verify the NTS integration test environment in WSL. Use when Codex is asked to run, fix, or document NTS.Tests.Integration in WSL; install or repair Azure Functions Core Tools for this repo; create a WSL func shim; use Docker Desktop from WSL; start Azurite; or diagnose integration harness startup failures involving func, Docker, Azurite, MongoDB connection strings, or WSL localhost. Use when this capability is needed.---# NTS WSL Integration## Core RuleRead the repository `AGENTS.md` before making changes. If it forbids writes outside the working directory, ask the user to lift that rule before creating `~/.local/bin/func` or editing `~/.bashrc`.## Use The Linux Func PathPrefer Linux Azure Functions Core Tools under the repository `.tools/` directory. Do not rely on Windows `func.exe` for the integration harness: it can start the Functions host, but WSL may not reach the Windows loopback listener at `127.0.0.1:<port>`.Use Docker Desktop's WSL CLI whenever Docker is needed:```bash/mnt/wsl/docker-desktop/cli-tools/usr/bin/docker```## Setup WorkflowFrom the repository root:1. Verify the repo rules:```bashsed -n '1,180p' AGENTS.md```2. If home-directory writes are allowed or the user explicitly lifts the rule, run the setup script:```bashbash .codex/skills/nts-wsl-integration/scripts/setup_wsl_integration.sh```3. If home-directory writes are not allowed yet, install only repo-local tools first:```bashbash .codex/skills/nts-wsl-integration/scripts/setup_wsl_integration.sh --skip-shim --skip-bashrc```4. Verify without modifying files:```bashbash .codex/skills/nts-wsl-integration/scripts/setup_wsl_integration.sh --verify-only```5. Run the integration project with the expected output levels:```bashPATH="/mnt/wsl/docker-desktop/cli-tools/usr/bin:$HOME/.local/bin:$PATH" dotnet build tests/NTS.Tests.Integration/NTS.Tests.Integration.csproj -v:qPATH="/mnt/wsl/docker-desktop/cli-tools/usr/bin:$HOME/.local/bin:$PATH" dotnet test tests/NTS.Tests.Integration/NTS.Tests.Integration.csproj -v:m```## Expected Installed Pieces- `.tools/node`: local Linux Node runtime used for npm/extraction.- `.tools/npm`: local npm prefix containing `azure-functions-core-tools`.- `.tools/npm/node_modules/azure-functions-core-tools/bin/func`: Linux `func` binary.- `~/.local/bin/func`: optional shim pointing at the repository-local Linux `func`.- `~/.bashrc`: optional PATH line placing Docker Desktop's WSL CLI and `~/.local/bin` first.`.tools/` is local machine state and should stay git-ignored.## Common Failures- `func: command not found`: create or repair the shim after user approval for home-directory writes.- Docker reports `client version 1.43 is too old`: use `/mnt/wsl/docker-desktop/cli-tools/usr/bin/docker` instead of `/usr/bin/docker`.- `MongoDB connection string is null`: usually caused by launching Windows `func.exe`; switch to Linux `func`.- `Nexus HTTP did not become healthy` while Functions lists routes: often Windows `func.exe` loopback isolation; switch to Linux `func`.- Azurite storage errors: start the `azurite` Docker container on ports `10000`, `10001`, and `10002`.## Script NotesThe setup script downloads a large Functions Core Tools zip from Microsoft's CDN and extracts about 1.3 GB under `.tools/`. This can be slow on `/mnt/*` drives. Prefer checking whether `.tools/npm/node_modules/azure-functions-core-tools/bin/func --version` works before repeating the download.---> Source: [Not-Endurance/not-timing-system](https://github.com/Not-Endurance/not-timing-system) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions