Lists exact files that would be uploaded to npm, helping catch missing or unwanted inclusions before publish
Respects files field in package.json, .npmignore , and .gitignore rules to show the actual bundle contents
Automatically builds the package, creates a tarball, displays contents, and cleans up in a single command
Run from the package directory with a simple bash script; useful f
No content available.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionlist-npm-package-contentExecute the skills CLI command in your project's root directory to begin installation:
Fetches list-npm-package-content from vercel/ai and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate list-npm-package-content. Access via /list-npm-package-content in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
23.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.3K
stars
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sickn33/antigravity-awesome-skills
aaron-he-zhu/seo-geo-claude-skills
aaaaqwq/claude-code-skills
hvpandya/stop-slop
JuliusBrussee/caveman
JuliusBrussee/caveman
list-npm-package-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: list-npm-package-content is the kind of skill you can hand to a new teammate without a long onboarding doc.
list-npm-package-content reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added list-npm-package-content from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: list-npm-package-content is focused, and the summary matches what you get after install.
list-npm-package-content has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend list-npm-package-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in list-npm-package-content — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
list-npm-package-content has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: list-npm-package-content is focused, and the summary matches what you get after install.
showing 1-10 of 29