list-npm-package-content

List npm package tarball contents before publishing.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/titabash/gemini-hackathon-game --skill list-npm-package-content-titabash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-npm-package-content
Source: https://github.com/titabash/gemini-hackathon-game/tree/main/.agents/skills/list-npm-package-content
Command: npx skills add https://github.com/titabash/gemini-hackathon-game --skill list-npm-package-content-titabash

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pnpm, and includes scripts (resource) components.

What problem does it solve?

This skill helps developers verify the exact files that will be included in an npm package before publishing, preventing unexpected inclusions or omissions.

Core Features & Use Cases

  • Pre-publish Verification: See precisely what files npm publish will upload.
  • Debugging Publish Issues: Identify why a package might be larger than expected or missing crucial files.
  • Use Case: Before publishing a new version of a library, run this skill to ensure only the intended source files, compiled assets, and necessary metadata are included in the tarball.

Quick Start

Run the list-package-files.sh script from your package directory.

Frequently Asked Questions about list-npm-package-content

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which files are included in an npm package before publishing?

To inspect npm package contents before publishing, list the tarball files generated by your pack configuration. This verifies exactly what `npm publish` will upload, preventing unexpected file inclusions or omissions.

Why does my npm publish include unexpected files in the tarball?

Your npm publish includes unexpected files in the tarball due to misconfigured `package.json` or `.npmignore` settings. Inspecting the tarball contents before publishing helps identify why a package might be larger than expected or missing crucial files.

How do I debug missing files in my npm package tarball?

To debug missing files in your npm package tarball, inspect the package contents before publishing. This helps identify why crucial files are excluded by checking the interactions between `package.json`, `.npmignore`, and default inclusions.

Do I need pnpm to inspect npm package tarball contents?

Yes, you need pnpm to inspect npm package tarball contents using this specific approach. The process requires pnpm for building the package and packing it into a tarball to verify the included files.

What is the best way to verify package.json and .npmignore rules for npm publish?

The best way to verify `package.json` and `.npmignore` rules for npm publish is to inspect the resulting tarball contents. This allows you to see precisely which files `npm publish` will upload based on your current configuration.