Git-Based Node Package Install

Use this skill when the main question is "what install packet should we trust, what delivery path fits this dependency, and what should we do next?"

The job is not to dump every syntax variant or treat raw Git installs as normal infrastructure. The job is to:

1. normalize the package-delivery packet already in hand,
2. choose one primary delivery mode,
3. make durability, auth, and build consequences explicit,
4. tailor commands to the package manager actually in use,
5. leave a clear exit path when a temporary Git bridge is starting to become permanent.

Read references/intake-packets-and-route-outs.md before handling an unfamiliar delivery packet. Read references/delivery-decision-matrix.md when deciding between Git, tarball, workspace, or publish-first. Read references/package-manager-behavior.md for manager-specific caveats. Read references/private-auth-and-ci.md when CI or private auth is already part of the packet.