sandbox-npm-install

Use this skill whenever:

github/awesome-copilot|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

Installation Guide

Select your AI agent

How to use sandbox-npm-install on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add sandbox-npm-install

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/github/awesome-copilot --skill sandbox-npm-install

Fetches sandbox-npm-install from github/awesome-copilot and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/sandbox-npm-install

Restart Cursor to activate sandbox-npm-install. Access via /sandbox-npm-install in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

When to Use This Skill

Use this skill whenever:

You need to install npm packages for the first time in a new sandbox session

package.json or package-lock.json has changed and you need to reinstall

You encounter native binary crashes with errors like SIGILL, SIGSEGV, mmap, or unaligned sysNoHugePageOS

The node_modules directory is missing or corrupted

Background

Docker sandbox workspaces are typically mounted via virtiofs (file sync between the host and Linux VM). Native Go and Rust binaries (esbuild, lightningcss, rollup, etc.) crash with mmap alignment failures when executed from virtiofs on aarch64. The fix is to install on the container's local ext4 filesystem and symlink back into the workspace.

Step-by-Step Installation

Run the bundled install script from the workspace root:

bash scripts/install.sh

Common Options

Option

Description

--workspace <path>

Path to directory containing package.json (auto-detected if omitted)

--playwright

Also install Playwright Chromium browser for E2E testing

What the Script Does

Copies package.json, package-lock.json, and .npmrc (if present) to a local ext4 directory

Runs npm ci (or npm install if no lockfile) on the local filesystem

Symlinks node_modules back into the workspace

Verifies known native binaries (esbuild, rollup, lightningcss, vite) if present

Optionally installs Playwright browsers and system dependencies (uses sudo when available)

If verification fails, run the script again — crashes can be intermittent during initial setup.

Important Notes

The local install directory (e.g., /home/agent/project-deps) is container-local and is NOT synced back to the host

The node_modules symlink appears as a broken link on the host — this is harmless since node_modules is typically gitignored

Running npm ci or npm install on the host naturally replaces the symlink with a real directory

After any package.json or package-lock.json change, re-run the install script

Do NOT run npm ci or npm install directly in the mounted workspace — native binaries will crash

Troubleshooting

Problem

Solution

SIGILL or SIGSEGV when running dev server

Re-run the install script; ensure you're not running npm install directly in the workspace

node_modules not found after install

Check that the symlink exists: ls -la node_modules

Permission errors during install

Ensure the local deps directory is writable by the current user

Verification fails intermittently

Run the script again — native binary crashes can be non-deterministic on first load

sandbox-npm-install

Installation Guide

How to use sandbox-npm-install on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

Sandbox npm Install

When to Use This Skill

Prerequisites

Background

Step-by-Step Installation

Common Options

What the Script Does

Post-Install Verification

Important Notes

Troubleshooting

Vite Compatibility

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

premium-frontend-ui

java-springboot

grill-me

premortem

deslop

framer-motion

Reviews

Discussion