Set up on Windows

Install the skills on Windows, with or without Node.js.

🔧 Prerequisites

Node.js 24.22.1 or later, for the first route
Git, for the second route

No administrator rights are needed either way.

📝 Steps — with Node.js

Install the CLI and run it, exactly as on Linux or macOS:
powershell
```
npm install -g ezai-marketplace
ezai install
```
1
2

📝 Steps — without Node.js

Clone the repository:

powershell

git clone https://github.com/neuraaak/ezai-marketplace.git
cd ezai-marketplace

Run the bundled batch script, which reproduces ezai install:

bat

scripts\install.bat                   REM all skills
scripts\install.bat <skill>           REM a single skill
scripts\install.bat <skill> <dest>    REM into a custom destination
scripts\install.bat "" <dest>         REM all skills, custom destination

When <dest> is omitted, %USERPROFILE% is used.

✅ Result

The skills are installed in %USERPROFILE%\.agents\skills\, and a junction is created in .claude\skills\ when that directory exists. The other agents read the shared store directly and get no junction.

With the three-argument form, both the store and the junction are placed under <dest>, not under your profile — unlike ezai install, which always links under your home directory.

Windows cannot create symbolic links without elevated rights, so ezai uses directory junctions instead, automatically and with no configuration. The agents cannot tell the difference.

The batch script copies the same files as ezai install — SKILL.md and references\ — but it has no list, search, info, uninstall or purge counterpart. For those, install Node.js and use the CLI.

Set up on Windows ​

🔧 Prerequisites ​

📝 Steps — with Node.js ​

📝 Steps — without Node.js ​

✅ Result ​

➡️ Next steps ​

Set up on Windows

🔧 Prerequisites

📝 Steps — with Node.js

📝 Steps — without Node.js

✅ Result

➡️ Next steps