agentleFS
Sign inStart free
MelvynxMelvynx/ai-maxxing-skills/skills/setup-node/SKILL.md

setup-node

Skill32 starsChanged 23 days agoMITView on GitHub

Install Homebrew (macOS) and Node.js with npm on macOS, Linux or Windows, so npx, npm install -g and the CLIs that need them work. Use when node, npm or npx is missing or "command not found", or before setup-cloudflare, setup-convex, setup-lumail or setup-dev-browser.

  • Installs packages

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check first: if node --version prints v20 or higher and npm --version works, say so and stop.

    line 10
  2. Very specific:

    If the Mac account is not an admin and the install refuses, skip Homebrew and pass --no-brew to the install scripts of every setup skill.

    line 18
  3. Very specific:

    Make sure global installs work without admin rights: run npm config get prefix.

    line 24

≈ “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

Get a working Node.js LTS with npm and npx for the current user. Do it yourself and only ask the user for what needs a human. Talk to them in their language, short messages, no jargon (never say "PATH", "prefix" or "LTS" to them).

If you got this skill from a link instead of a local folder, install nothing else from the repo: download a file it links only when a step needs it, with curl -fsSL https://raw.githubusercontent.com/Melvynx/ai-maxxing-skills/main/skills/setup-node/<path> -o <scratch>/<file> (for example scripts/install-node.sh), and read another skill it names only when you reach it, from https://raw.githubusercontent.com/Melvynx/ai-maxxing-skills/main/skills/<skill-name>/SKILL.md.

  1. Check first: if node --version prints v20 or higher and npm --version works, say so and stop.
  2. Find the OS with uname -s (Darwin is macOS, Linux is Linux); if it fails or PowerShell answers, it is Windows.

  3. On macOS, make sure Homebrew is there: it is the one way every setup skill installs tools on a Mac, it also installs Apple's developer tools (Git), and it keeps everything up to date. Look for /opt/homebrew/bin/brew (Apple Silicon) or /usr/local/bin/brew (Intel), even if brew is not found. If neither exists, Homebrew needs the user's Mac password once, so you cannot run it yourself: ask them to open the Terminal app (Cmd+Space, type "Terminal"), paste the line below, press Enter, type their Mac password when asked (nothing shows while typing, that is normal), press Enter again when it asks, and say "done" when it finishes (5 to 15 minutes).

    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

    If the Mac account is not an admin and the install refuses, skip Homebrew and pass --no-brew to the install scripts of every setup skill.

  4. Install:

    • macOS and Linux: run scripts/install-node.sh. On macOS it uses brew install node and writes Homebrew into the shell config so new sessions find it; it exits with code 3 if Homebrew is missing (go back to step 3). On Linux, or with --no-brew, it downloads the official Node LTS into ~/.local/node with no admin password.
    • Windows: winget install --id OpenJS.NodeJS.LTS -e --accept-source-agreements --accept-package-agreements, then ask the user to close and reopen the Claude session.

    The current session does not see the new install yet: prefix your next commands with eval "$(/opt/homebrew/bin/brew shellenv)" (or /usr/local/bin/brew on Intel) on macOS, or export PATH="$HOME/.local/node/bin:$PATH" with the ~/.local install.

  5. Make sure global installs work without admin rights: run npm config get prefix. If npm install -g fails with EACCES, run npm config set prefix ~/.local and make sure ~/.local/bin is in the shell config. Never use sudo npm.
  6. Prove it: node --version && npm --version && npx --version, then npx -y cowsay ok prints a cow. Then check a new session finds it too: $SHELL -lic 'node --version' prints the same version; if not, fix the shell config before going on.

Reply with the Node version and where it is installed, in one line.

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.

Check your setup, free