List Npm Package Content

Before you publish to npm, you want to know exactly what files you're shipping. This skill runs a quick tarball inspection to show you the actual contents that would be distributed, which is surprisingly different from what's in your repo if you've got npmignore rules or a files field in package.json. It's the "measure twice, cut once" check for package authors. Saves you from accidentally publishing source maps, test fixtures, or private config files to the registry, or worse, discovering you forgot to include the dist folder. Run it from your package directory and it handles the build, tarball creation, listing, and cleanup automatically.