Most npm-from-Git questions aren't really about Git syntax. They're about whether that branch pin should become a SHA, whether the monorepo package should stay a workspace link, or whether the "temporary" fork install should finally get published. This skill routes you through six delivery modes (direct Git bridge, SHA-pinned shared bridge, private auth path, tarball artifact, workspace link, or publish-first registry) based on who's consuming it, whether CI needs it, and what happens when the dependency stops being temporary. It's opinionated about durability tiers and makes auth and build consequences explicit before handing you a command. Use it when the real question is which install packet to trust, not how package managers work in general.
npx -y skills add akillness/oh-my-skills --skill npm-git-install --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
cursor/plugins
github/awesome-copilot
alirezarezvani/claude-skills
microsoft/win-dev-skills