npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@prevu/skills

v0.3.3

Published

Agent skills for Prevu — install with `npx skills sync` to teach Claude Code, Cursor, etc. how to drive the Prevu CLI.

Readme

@prevu/skills

Agent skills for Prevu — drop-in instructions that teach Claude Code, Cursor, OpenHands, and other coding agents how to drive the Prevu CLI.

Install

npm install -D @prevu/skills

# Sync into your agent of choice
npx skills experimental_sync -a claude-code
# or: -a cursor / -a openhands / etc.

This symlinks the skills from node_modules/@prevu/skills/skills/ into the agent's skills directory.

Alternative — install from the GitHub mirror without npm:

npx skills add prevu-cloud/prevu-skills -a claude-code

What you get

Two skills, designed around how agents actually load context (description always-on; body on trigger; references on-demand):

prevu

The reference skill. Triggers when the user mentions Prevu, the CLI, env work, tokens. Body is a short overview + command map; deep detail lives in references/:

  • references/auth.md — sign-in, token storage, recovering from auth errors.
  • references/env.md — every env subcommand with examples + SSH key resolution rules.
  • references/keys.md — saved SSH key model.
  • references/lifecycle.md — status state machine and destructive-action guidance.
  • references/troubleshooting.md — concrete failure modes and fixes.

prevu-flows

The workflow skill. Triggers on multi-step user scenarios:

  • references/mirror-dev.mdAFK loop: mirror local dev to a Prevu env so the user can preview changes from their phone while iterating with the agent in chat. Edit-locally → push → env-pulls → preview → review → repeat.
  • references/share-preview.md — share a WIP branch as a public preview URL for a teammate, designer, PM, or future-self on another device.

Why two skills, not five

Skills compete for "always-on" context budget via their description. Anthropic's own skill-creator guidance pushes domain organization (one skill per domain, references on-demand) over command-per-skill splits. Prevu's auth/env/keys always co-occur — splitting them just multiplies the always-on tax. The flows are scenario-narrative with distinct trigger phrases, so they get their own skill.

Versioning

Independent SemVer (0.2.0 at launch). Tracks CLI majors (0.x skills with 0.x CLI).

License

MIT