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

genizah

v0.1.2

Published

Install Genizah agent skills.

Downloads

498

Readme

Genizah CLI

Overview

Genizah is a catalog of self-contained specification bundles: algorithms, strategies, and acceptance scenarios that an AI agent can adapt to a concrete implementation. The CLI installs the genizah and customize-spec-bundle skills into your project; bundles stay in the catalog until you choose one.

Example

Install the skills in the project where you want to use a bundle, then ask your agent to find and integrate one:

Use the genizah skill to search for a spec bundle that does
<whatever you're thinking of> for this project and integrate the bundle I
confirm.

The skill inspects the project, recommends a bundle, and waits for your confirmation before it starts customization.

Installation

Install the Genizah discovery and customization skills in a project:

npx --yes genizah init

The command lets you select one project-level skill location. It defaults to .agents/skills and also supports .github/skills, .claude/skills, .cursor/skills, .codex/skills, .opencode/skills, and .pi/skills. Pass --skills-dir RELATIVE_PATH to select a contained project path without a prompt.

If a target skill directory belongs to another tool, init leaves it unchanged and tells you which directory blocked installation. Re-run with --force (or -f) only when you intend to replace that directory:

npx --yes genizah init --force

Before the catalog is published, install from a local Genizah checkout while standing in the target project:

npm --prefix ../genizah/tooling/npm run local:init -- .

local:init resolves . from the invoking directory, reads the skills from that checkout, and makes no network request. It accepts the same --skills-dir --force, and -f options as init. The installed genizah skill uses the local catalog for discovery:

To replace a conflicting target skill directory during local development, use the same force flag as the published command:

npm --prefix ../genizah/tooling/npm run local:init -- . --force
npm --prefix ../genizah/tooling/npm run local:search -- procedural maps

Search the GitHub-hosted catalog with JSON-only output:

npx --yes genizah search procedural maps

The installed genizah skill recommends a bundle but waits for confirmation. After confirmation, it hands the selected bundle to customize-spec-bundle which reviews your code context and asks clarifying questions before generating customized specs.