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

85%

Does it follow best practices?

Impact

100%

1.47x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, actionable, and well-structured for a simple skill, with a real referenced script. The main gap is workflow clarity: the destructive cleanup step lacks validation or a retry loop, which the rubric caps at 3.

Suggestions

Add an explicit validation step after packing (e.g. verify the tarball path is non-empty before listing) and wrap the `rm` cleanup so it only runs after listing succeeds.

Document an error-recovery feedback loop: if `pnpm pack` output parsing fails or the tarball is missing, surface a clear message instead of letting `set -e` abort silently.

Note prerequisites/assumptions (pnpm available, run from package directory) explicitly in the body so the single command is unambiguous to execute.

Dimension	Reasoning	Score
Conciseness	The body is lean (~25 lines) with no padding or over-explanation of npm basics; the factual always-included/excluded list is reference material Claude would not reliably know, so each token earns its place.	5 / 5
Actionability	It gives a copy-paste-ready command ("bash scripts/list-package-files.sh") backed by an executable script (pnpm build; pnpm pack; tar -tzf; rm) that covers the common case completely.	5 / 5
Workflow Clarity	The build->pack->list->cleanup sequence is present but has no validation checkpoints or error-recovery feedback loop despite a destructive `rm "$tarball"` cleanup and `set -e`, so the destructive-operation cap applies.	3 / 5
Progressive Disclosure	A simple single-purpose skill under 50 lines with well-organized sections and a correctly referenced real bundle script (scripts/list-package-files.sh), satisfying the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it states a concrete action, gives explicit trigger guidance with natural user phrases, and occupies a clearly distinct niche. Its only modest gap is specificity breadth, since it centers on a single primary action rather than a comprehensive set.

Dimension	Reasoning	Score
Specificity	"List the contents of an npm package tarball before publishing" names the domain and one concrete action (listing contents), matching the anchor for naming a domain with 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly answers both what (list tarball contents before publishing) and when ("Use when the user wants to see what files are included...verify package contents, or debug npm publish issues") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like "npm package tarball", "npm bundle", and "npm publish" map to what users would say, giving good keyword coverage, though a few synonyms (e.g. .tgz) are missing.	4 / 5
Distinctiveness Conflict Risk	The npm-package-tarball inspection niche is distinct with specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: vercel/ai
Path: skills/list-npm-package-content/SKILL.md
Commit: 86892f3

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.