list-npm-package-content

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.

1.47x

Quality

73%

Does it follow best practices?

Impact

100%

1.47x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/list-npm-package-content/SKILL.md

Evaluation results

100%

31%

Automate Pre-Publish Package Inspection

Package listing script creation

Criteria

Without context

With context

Correct shebang

100%

Exit on error

100%

Build step uses pnpm

100%

Pack step uses pnpm

100%

Tarball filename capture

53%

100%

List without extract

100%

Tarball variable used

100%

Tarball cleanup

100%

Run from package dir

100%

Document npm Package File Inclusion Behavior

npm file inclusion rules knowledge

Criteria

Without context

With context

files field as allowlist

100%

.npmignore for exclusions

100%

.gitignore fallback

100%

package.json always included

100%

README always included

100%

LICENSE always included

100%

CHANGELOG always included

100%

.git excluded

100%

node_modules excluded

100%

.npmrc excluded

100%

Concrete examples used

100%

Precedence relationship

100%

65%

Set Up Pre-Publish Verification in a Monorepo

Monorepo package verification workflow

Criteria

Without context

With context

Correct script invocation

46%

100%

cd into package dir

100%

PUBLISHING.md: cd instruction

100%

PUBLISHING.md: build documented

30%

100%

PUBLISHING.md: tarball creation

100%

PUBLISHING.md: cleanup

100%

pnpm referenced

100%

Bash best practices

100%

Repository: vercel/ai
Commit: 48f65f5

Evaluated: about 1 month ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Automate Pre-Publish Package Inspection Document npm Package File Inclusion Behavior Set Up Pre-Publish Verification in a Monorepo

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.