npm-git-install
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
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that follows best practices. It uses third person voice, provides specific concrete actions, includes an explicit 'Use when' clause with relevant trigger scenarios, and carves out a distinct niche that won't conflict with general npm or GitHub skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Install npm packages directly from GitHub repositories using git URLs' with clear use cases including 'private repos, specific branches, or unreleased versions not yet on npm registry'. | 3 / 3 |
Completeness | Clearly answers both what ('Install npm packages directly from GitHub repositories using git URLs') and when ('Use when installing packages from private repos, specific branches, or unreleased versions not yet on npm registry') with explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'npm packages', 'GitHub repositories', 'git URLs', 'private repos', 'specific branches', 'unreleased versions', 'npm registry'. Good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focusing specifically on GitHub-based npm installation via git URLs, distinct from general npm package management or GitHub operations. The combination of npm + GitHub + git URLs creates a unique trigger profile. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable guidance for npm git installations with excellent concrete examples and commands. However, it's overly verbose for Claude's needs, explaining concepts like internal npm operations and platform paths that Claude already knows. The workflow could benefit from integrated validation steps rather than separate troubleshooting sections.
Suggestions
Remove sections explaining what Claude already knows: internal npm operations, platform-specific paths table, basic git installation commands
Integrate validation steps into the main workflow (e.g., 'After install, verify with: npm list -g <package> && which <command>')
Move 'Common Errors & Solutions' to a separate TROUBLESHOOTING.md file and reference it
Remove the Metadata section entirely - version numbers, dates, and tags don't help Claude execute the skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful information but is verbose with sections Claude already knows (e.g., explaining what npm does internally, platform-specific paths, basic git installation commands). The metadata section at the end and extensive best practices add bulk without proportional value. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout. Syntax examples are concrete with real repository URLs, specific flags, and complete command structures. The package.json examples are directly usable. | 3 / 3 |
Workflow Clarity | The 'npm install Flow' section shows the sequence but lacks validation checkpoints. There's no explicit 'verify installation worked' step integrated into workflows, and error recovery is listed separately rather than as feedback loops within the process. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear headers, but it's monolithic - everything is in one file when sections like 'Common Errors & Solutions' or 'Private Repositories' could be separate references. The references section at the end is good but internal structure could benefit from splitting. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- Reviewed
Table of Contents
Is this your skill?
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.