ns-node-upgrade

From README

Get the Authoritative Release Schedule Before reasoning about LTS or EOL dates, fetch live data (use the absolute path of the directory where you read this SKILL.md): The script prints a markdown table fetched from endoflife.date (with an offline fallback): If a release schedule table is already injected into the prompt by the host (labelled AUTHORITATIVE Node.js release schedule), use it verbatim — do not run the script, do not substitute values from your training data. In all cases: treat the table as the source of truth for LTS names, EOL dates, and latest patch versions. Do not override it with training-data values. Detect the Current Node.js Version If detection results are already provided in the prompt (labelled Detected Node.js version information), use those results and skip manual detection. Otherwise, check in order: package.json → engines.node field (project pin — authoritative for the project). .nvmrc file in the workspace root. .node-version file in the workspace root.