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.
94
Does it follow best practices?
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with explicit 'Use when' guidance and good trigger term coverage for npm-related queries. The main weakness is that it only describes one action (listing contents) rather than multiple specific capabilities. Overall, it should effectively distinguish itself from other skills and trigger appropriately.
Suggestions
Add more specific actions beyond 'list contents', such as 'inspect file sizes', 'verify .npmignore rules', or 'compare expected vs actual bundle contents'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (npm package tarball) and one action (list contents), but doesn't list multiple concrete actions. Could specify actions like 'inspect file sizes', 'check for missing files', or 'compare against .npmignore'. | 2 / 3 |
Completeness | Clearly answers both what ('List the contents of an npm package tarball before publishing') and when ('Use when the user wants to see what files are included in an npm bundle, verify package contents, or debug npm publish issues'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'npm package', 'tarball', 'publishing', 'npm bundle', 'package contents', 'npm publish'. These are terms users would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on npm package tarballs and publishing. Unlikely to conflict with general file listing or other package manager skills due to explicit npm-specific terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, focused skill that does one thing clearly. It provides an immediately actionable command, explains what the script does, and includes helpful context about npm's file inclusion rules without over-explaining. The content respects Claude's intelligence while providing the specific project knowledge needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It provides only essential information without explaining what npm is or how tarballs work. Every section earns its place. | 3 / 3 |
Actionability | Provides a concrete, copy-paste ready command with clear context about where to run it. The single bash command is fully executable. | 3 / 3 |
Workflow Clarity | For this simple single-task skill, the workflow is unambiguous: run one script that handles build, tarball creation, listing, and cleanup automatically. No multi-step validation needed for a read-only listing operation. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized with clear sections (Usage, Understanding). The reference information about package.json fields is appropriately inline given its brevity. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 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 |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
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.