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

@cleepi/toolkit

v0.3.3

Published

The Cleevio agent in one install. Bundles @cleepi/sdd, base, coding, git, crew, atlassian, and ships a `cleepi-toolkit init` CLI to wire them up in one command.

Downloads

1,255

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

honemhonem

Keywords

pi-packagecleepicleeviometa-package

Readme

@cleepi/toolkit

The Cleevio agent in one install. Pulls in every general-purpose Cleepi package and wires it up in a single command — no walk-through, no follow-up steps.

What's in the box

| Member | What it gives you | | --- | --- | | @cleepi/sdd | Spec-Driven Development workflow (/spec, /journal, /changelog, the cockpit) | | @cleepi/base | Cleevio voice + cleevio-dark theme | | @cleepi/coding | Cleevio coding craft + /review | | @cleepi/git | Branch / commit / PR conventions | | @cleepi/crew | Subagent crew and orchestration | | @cleepi/atlassian | Jira + Confluence access |

Plus this package's own additions:

  • cleepi-toolkit init — single-command installer. Runs pi install for the toolkit + pi-mcp-adapter, scans the resulting node_modules for transitively-installed pi-packages (atlassian, git, crew's peers — anything with a pi manifest), and registers them all in settings.json. Idempotent.
  • cleepi-setup skill — in-session help for users who want a guided walk-through (legacy /setup prompt is deprecated; see CHANGELOG).

Install

One command, inside a project directory:

cd <repo>
npx @cleepi/toolkit@latest init

Defaults: project scope (writes to ./.pi/settings.json), installs @cleepi/toolkit + pi-mcp-adapter. After it finishes, every cleepi skill is loaded on your next pi session in this project.

User scope (available in every project on the machine):

npx @cleepi/toolkit@latest init --user

Custom packages (advanced):

npx @cleepi/toolkit@latest init npm:@cleepi/crew

Why a polyfill?

pi install itself only registers the explicitly-named package in settings.json — npm correctly auto-installs peer pi-packages, but pi doesn't reflect them in its own registry, so their skills don't load. cleepi-toolkit init scans + registers them, with collision detection so packages already exposed via another's pi manifest (e.g. @cleepi/base via toolkit's bundle) aren't double-registered. Upstream pi fix tracked separately.

À la carte

If you want a leaner install, install members individually — see the root README. The à la carte path stays supported; toolkit is just the friction-free default.

Related