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

tool-librarian

v1.0.0

Published

Install the Tool Librarian skill for Claude. Keeps a curated library of tools you have vetted and recommends from your own picks first.

Readme

Tool Librarian

A Claude skill that keeps a curated library of the tools you have actually vetted, and answers "what should I use for X" out of that library before it reaches for anything else.

You find a good tool, you bookmark it, you forget it, and six months later you google the same question and land on a worse answer. This is the fix for the forgetting half.

Install

Either route installs the skill. Pick whichever fits where you use Claude.

In Claude Code, as a plugin:

/plugin marketplace add jainulabudeenm/tool-librarian
/plugin install tool-librarian

From npm, which also covers Claude.ai and anywhere outside Claude Code:

npx tool-librarian

Add --project to install into the current repo instead of your home directory, so you can commit it and share it with a team.

Use

Drop a link.

> add this to my toolbox: https://raycast.com

It drafts the entry, picks a cluster, and asks you to confirm before writing anything.

Then ask for it back.

> what is the best tool for cleaning up a screen recording?

It answers from your library first, names the tool and why it fits this job, and only reaches outside when there is a genuine gap. Anything from outside is labelled as a suggestion, so a vetted pick and a guess never look the same.

Clusters are by vibe, not by function

This is the only opinionated part, and it is what keeps the library usable past fifty entries.

A functional taxonomy sorts by what a tool technically is. Editors here, APIs there, design tools in the third box. It reads tidy and it fails in practice, because it splits up tools you reach for in the same state of mind and shelves together tools you would never consider in the same breath.

Clustering by vibe sorts by the mode you are in when you go looking. You are not thinking "I need a design tool", you are thinking "the visual decision is the hard part today". The library should be organised the way the question arrives.

You get a starter set on first run. Rename it, gut it, grow it. When something genuinely does not fit, the skill proposes a new cluster rather than stretching an old one, because a cluster that means everything means nothing.

The library

~/.claude/tool-librarian/library.md, in your home directory rather than a project folder, so it follows you rather than the repo. Plain markdown, yours to edit by hand whenever you like.

There is no setup step. First run creates the file and gets on with your request. See library.example.md for the shape and the level of detail that makes recall useful.

Not for

Notes, meeting records, or saved conversations. This is one file about one subject. It stays good by staying narrow.

License

MIT