Install npm packages directly from GitHub repositories using git URLs. Use when installing packages from private repos, specific branches, or unreleased versions not yet on npm registry.
85
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Git URL dependency pinning
Uses git+https: or github: prefix
100%
100%
No #main or #master in production dep
100%
100%
Pinned to specific tag or commit
100%
100%
Correct .git suffix in URL
100%
100%
Dependency in package.json
100%
100%
Verify git prerequisite
100%
100%
Lockfile commitment mentioned
100%
100%
No token hardcoded
100%
100%
Installation command correct
80%
100%
Private repo auth configuration
SSH key method covered
0%
100%
SSH keygen uses ed25519
0%
100%
PAT stored in env var
100%
100%
No hardcoded token in package.json
100%
100%
.npmrc auth configuration
100%
100%
SSH git URL format
0%
100%
PAT URL format correct
0%
100%
SSH connection test mentioned
0%
100%
No tokens in logs or output
100%
62%
Auth method compared or recommended
0%
100%
Installation troubleshooting workflow
Uses --verbose flag
0%
100%
No sudo for permission fix
100%
100%
npm config set prefix used
100%
100%
PATH update for new prefix
100%
100%
npm cache clean used
100%
100%
TypeScript prepare fix
100%
100%
Uninstall before reinstall
0%
100%
Git install verification
100%
100%
Verbose log captured to file
0%
100%
Checklist covers multiple error types
100%
100%
c033769
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.