agentleFS
Sign inStart free
niksavisniksavis/handily/.agents/skills/node/SKILL.md

node

Skill2 starsChanged 31 days agoMITView on GitHub

Runs Node and npm for the markdownlint hook and other tools. Use when npm or npx fails or resolves the wrong node binary, often on WSL.

  • Installs packages

10 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use java and rust.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • testdino-hqSkill

    java

    Google's official Java style guide. Covers 2-space indentation, 100-char line limit, naming conventions, braces, imports, Javadoc, exception handling, lambdas, and streams. Enforces @Override annotations and specific imports.

    Also in 3 projects that use this

  • MicrosoftSkill

    rust

    Use this guide when working on Rust changes in the FAST monorepo.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Run node tooling so that it uses the Linux node and the pinned packages.

    line 9
  2. Very specific:

    Only an explicit configuration opts out.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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
<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. -->

Node

Run node tooling so that it uses the Linux node and the pinned packages. The markdownlint git hook needs markdownlint-cli2 from package-lock.json.

Rules

  • Install with npm ci, not npm install. It installs exactly what package-lock.json pins. Commit the lockfile with each dependency change.
  • Run a tool with npx --no-install <tool>. It runs the pinned local package and refuses to download a different version.
  • Put the Linux node on PATH before a script or background job runs node or npx. A non-interactive shell does not load nvm, so WSL can find a Windows node instead.
  • Ask before you add a dependency. It is on the confirmation list.

The markdownlint hook

The hook finds node itself and never calls npx. It uses the first usable node from this list, and never a Windows node under /mnt:

  1. node on PATH
  2. the newest node under nvm ($NVM_DIR, or ~/.nvm)
  3. /usr/local/bin/node, then /usr/bin/node

The hook and basicly install refuse missing prerequisites before reporting success. Install checks before writing files, including with --dry-run. Read the refusal:

MessageFix
node_modules/markdownlint-cli2/... is missingRun npm ci when the package is locked. Otherwise get approval, then run npm install --save-dev markdownlint-cli2 and commit the package files.
no usable node found on PATH, under nvm, or in /usr/binInstall a Linux node, for example nvm install --lts.

The enabled hook reads inputs from the repository's .markdownlint-cli2.jsonc, .markdownlint-cli2.yaml, .markdownlint-cli2.cjs or .markdownlint-cli2.mjs. A style-only .markdownlint.json file does not select CLI2 inputs. Keep existing input and rule choices; install creates no Markdown policy. Before a first commit, configure real consumer Markdown inputs. The first-loop tutorial explicitly chooses README.md and NOTES.md, with a clean README and every default rule enabled.

Only an explicit configuration opts out. The hook then prints markdownlint: opted out by hooks.markdownlint.enabled=false and exits 0:

[hooks.markdownlint]
enabled = false

The hook reads basicly.toml, sorted basicly.d/*.toml, then basicly.local.toml. Later settings win. A malformed setting refuses. A technology selection excluding Node does not install the markdown gate or require its runtime.

Node in a non-interactive shell on WSL

A script, a background job or a hook does not load your shell profile. Then node and npx can resolve to a Windows install. The fix is in references/wsl-node-path.md. The wsl skill covers the general interop model.

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