Lists exact files included in an npm package tarball based on package.json and ignore files.
Install
mkdir -p .claude/skills/list-npm-package-content && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/940" && unzip -o skill.zip -d .claude/skills/list-npm-package-content && rm skill.zipInstalls to .claude/skills/list-npm-package-content
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
List the contents of an npm package tarball before publishing. Use when the user wants to see what files are included in an npm bundle, verify package contents, or debug npm publish issues.Key capabilities
- →List files included in an npm package tarball
- →Verify package.json files field configuration
- →Identify files excluded by .npmignore or .gitignore
- →Simulate the npm publishing process
How it works
The skill builds the package and creates a temporary tarball to list exactly which files are included based on npm's inclusion rules.
Inputs & outputs
When to use list-npm-package-content
- →Verifying package.json files field
- →Debugging unexpected files in a published package
- →Checking npmignore effectiveness
About this skill
List npm Package Content
This skill lists the exact contents of an npm package tarball - the same files that would be uploaded to npm and downloaded by users.
Usage
Run the script from the package directory (e.g., packages/ai):
bash scripts/list-package-files.sh
The script will build the package, create a tarball, list its contents, and clean up automatically.
Understanding Package Contents
The files included are determined by:
filesfield inpackage.json- explicit allowlist of files/directories.npmignore- files to exclude (if present).gitignore- used if no.npmignoreexists- Always included:
package.json,README,LICENSE,CHANGELOG - Always excluded:
.git,node_modules,.npmrc, etc.
When not to use it
- →Publishing packages directly to the registry
Prerequisites
Limitations
- →Requires a valid package directory structure
How it compares
It allows developers to verify the contents of a package before publishing, preventing the accidental inclusion of unnecessary files.
Compared to similar skills
list-npm-package-content side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| list-npm-package-content (this skill) | 6 | 6mo | Review | Beginner |
| turborepo | 61 | 2mo | Review | Intermediate |
| shellcheck-configuration | 9 | 2mo | No flags | Intermediate |
| bazel-build-optimization | 14 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by vercel
View all by vercel →You might also like
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
shellcheck-configuration
wshobson
Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
e2e-testing-patterns
wshobson
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.