toolkit-map skill
toolkit-map tells an agent which copy of node, python or git to run on Windows and returns a verified absolute path.
- 111 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The quick start script edits project rules and MCP configuration and runs with an execution policy bypass for the child process.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/toolkit-mapDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The quick start script edits project rules and MCP configuration and runs with an execution policy bypass for the child process.
This is third-party code. Review the repository files before installing.
What it does
A map of installed tools for Windows. Before running `node`, `python` or `git`, the agent asks the map which version the project requires and which verified copies exist on the machine. Requirements come from `mise.toml`, `.tool-versions`, `.nvmrc` and the `engines` field in package.json, and copies are found in `PATH`, a shared store, the mise directory and manually registered locations. The answer holds `path`, `version`, `verification` and `requirement`. A query is read-only: it installs nothing, does not change `PATH` and does not guess a version. If no matching copy exists it returns `version_mismatch`, and an unclear requirement gives `requirement_unsupported`. Scanning, updating and adding are separate commands that need user consent. It connects to an agent through project rules and an optional MCP server on Node.js 18.
Who it is for. Developers on Windows with several Node, Python and Git versions on the machine where the agent runs the wrong one for the project.
Good fit when
- `PATH` holds Node 16 while the project requires Node 22.
- Several Python copies sit on the machine and the agent mixes them up.
- Project versions are declared in `mise.toml` or `.nvmrc` and must be honored at launch.
- You want a project where an agent gets a tool path through MCP instead of guessing.
Not a fit when
- You work on macOS or Linux: Windows with PowerShell 5.1 or 7 is supported.
- You need a version manager that installs tools itself.
- No version is declared and the newest one is wanted.
Example request
Use toolkit-map to find the Node version this project needs and show the absolute path, version and the requirement it was chosen by.Limitations
Windows only, with Windows PowerShell 5.1 or PowerShell 7, and Git is required. MCP mode additionally needs Node.js 18, while the map itself does not depend on Node. Version selection order: the `-Version` parameter, then the project declaration, then parent directory and global declarations, then the system default. The quick start script runs with `-ExecutionPolicy Bypass` for the child process only and does not change machine policy. The main documentation is in Chinese, with an English version.
How to disable. Remove the project rules, the MCP entry and skill links as the rollback guide describes. Already installed tools stay in place. Delete the `toolkit-map` clone folder by hand.
FAQ
Does the map pick the newest version?
No. The order is `-Version`, the project declaration, declarations higher in the tree, the system version. If `PATH` has Node 16, it returns 16.
Does the map change `PATH` or install tools?
No, a query only reads. Installation is a separate explicit `install` command.
Is mise required?
No. Without mise the map still discovers, registers and serves copies.
What does exit code 2 mean?
Rules are installed but MCP was not written, for example there is no Node 18 or the startup check failed.
How do I roll back?
Remove project rules, MCP configuration and skill links. Installed tools stay.
Discussion
No questions or reviews yet.
Related
SkillsA local agent runtime and MCP gateway with 298 tools: files, Git, processes, Chrome browser, Windows and Office
AWS's official set of MCP servers, skills and plugins so an agent can build, deploy and operate on AWS
CLI that runs commands and AI agents in isolated microVMs that boot in under 125 ms and keeps API keys out of the sandbox itself.
MCP server for Windows: the agent searches apps, tweaks and DNS in the WinUtil CN catalog; installs and edits need a flag and a confirmation
An agent guides a macOS install on an ordinary Windows PC: it checks hardware, prepares a USB drive and keeps Windows.
A CLI that installs shared skills, commands, subagents, hooks and MCP servers into eight AI coding tools in their native layouts
README in short
The README in Chinese and English covers the problem it solves, a quick start with a script and a manual route, exit codes, FAQ answers and links to the reference, MCP, platform notes and rollback.