Index of every page on this site: llms.txt
All skills
vercel avatar

/list-npm-package-content

@a8f0e9d official
by vercelvercel/ai28k stars
5,666
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/vercel/ai/list-npm-package-content

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈196 when used: this file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈216 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

  1. files field in package.json - explicit allowlist of files/directories
  2. .npmignore - files to exclude (if present)
  3. .gitignore - used if no .npmignore exists
  4. Always included: package.json, README, LICENSE, CHANGELOG
  5. Always excluded: .git, node_modules, .npmrc, etc.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7mo5 checks · Risk SAFE
  • Gen Agent Trust Hub8mo

    This skill provides a utility to inspect npm package contents before publication. It executes standard local development commands to build and list files within a tarball, ensuring the package contains only intended files. All operations are local and consistent with standard development workflows.

  • Socket8mo

    No alerts

  • Snyk8mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/2 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at a8f0e9d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 10 months ago
metadata
{
  "internal": true
}
  • Debugging
  • npm
  • packaging
  • vercel-ai
  • tarball
  • publish
  • node

README badge

README badge for vercel/ai/list-npm-package-content

Lists the exact files that will be included in an npm package tarball, using the package.json files field, .npmignore, and .gitignore to determine contents. Useful for verifying what gets published to npm or debugging unexpected inclusions before release.

Generated from the current SKILL.md.

What files does this skill include in the tarball?
The skill lists files based on the `files` field in package.json, .npmignore (or .gitignore if absent), plus always-included files like package.json, README, LICENSE, and CHANGELOG. It excludes .git, node_modules, .npmrc, and other standard npm-ignored paths.
Does this skill actually publish to npm?
No. It builds the package, creates a tarball, lists its contents, and cleans up locally. It does not upload anything to npm.
Can I use this outside the vercel/ai monorepo?
The skill is designed to run from a package directory with a standard npm setup. It should work with any package that has a package.json and uses npm's standard file inclusion rules.

Generated from the current SKILL.md. These answers refresh after source changes.