# npm-git-install

Picks a safe delivery path for a Node package coming from a branch, commit, fork or private repo. Useful when the question is whether to pull from Git at all.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 350 installs · ★ 50
- Author: akillness
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/akillness/jeo-skills/tree/HEAD/.agent-skills/npm-git-install/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/npm-git-install

## What it does

The skill turns a package-install request into a single delivery packet and names one primary mode: a temporary Git bridge, a SHA-pinned bridge for shared use, a private Git path with auth, a tarball or `npm pack` artifact, a workspace or `file:` link, or publishing to a registry. It then classifies how durable the dependency really is, from local-only up to release infrastructure, and tailors the command to the manager in use — npm, pnpm, Yarn or Bun.

Supporting references ship with it: `references/intake-packets-and-route-outs.md` for an unfamiliar packet, `references/delivery-decision-matrix.md` for choosing between Git, tarball, workspace and publish-first, `references/package-manager-behavior.md` for manager-specific caveats, and `references/private-auth-and-ci.md` when CI or private credentials are already involved. The skill runs with `Bash`, `Read`, `Write`, `Edit`, `Glob` and `Grep`.

It stays out of local Git repair, repo and release administration, environment setup and monorepo task automation — those belong to other skills. A plain registry dependency that only needs a version bump is outside its scope too.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill npm-git-install -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/npm-git-install/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/npm-git-install/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill npm-git-install -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/npm-git-install/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill npm-git-install -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/npm-git-install/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install akillness/jeo-skills npm-git-install
```

2. **Manually: put the files in place**
- File: `.github/skills/npm-git-install/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill npm-git-install -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/npm-git-install
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/npm-git-install/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill npm-git-install -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/akillness/jeo-skills/tree/HEAD/.agent-skills/npm-git-install/SKILL.md

## When to use it
- install an unreleased fix from a fork branch
- pin a Git dependency to one commit for teammates and CI
- wire up a private package with matching auth locally and in CI
- build a tarball with `npm pack` instead of installing from source
- decide between workspace linking and publishing for a monorepo package

## Example prompts
- Install this package from a fork branch — which delivery path should we use?
- Pin the Git dependency to a commit so CI stops breaking on branch drift
- The package lives in a monorepo: link it as a workspace or build a tarball?

## Similar
- [triage](https://affpapa.org/en/nevibecode/skills/triage.md) — skill · 990453 installs
- [code-review](https://affpapa.org/en/nevibecode/skills/code-review.md) — skill · 789521 installs
- [implement](https://affpapa.org/en/nevibecode/skills/implement.md) — skill · 774700 installs
- [git-guardrails-claude-code](https://affpapa.org/en/nevibecode/skills/git-guardrails-claude-code.md) — skill · 499069 installs
- [setup-pre-commit](https://affpapa.org/en/nevibecode/skills/setup-pre-commit.md) — skill · 489289 installs
- [scaffold-exercises](https://affpapa.org/en/nevibecode/skills/scaffold-exercises.md) — skill · 480196 installs

From the same set: [akillness/jeo-skills](https://affpapa.org/en/nevibecode/by/akillness/jeo-skills.md) — 29 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md