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

@jaxho/skill-evolver

v0.1.1

Published

CLI-backed system for iterating Codex skills

Readme

skill-evolver

CLI-backed workflow for iterating a local Codex skill repository.

Skill-first User Path

Install the Skill Evolver collection first:

npx --registry=https://registry.npmjs.org skills add jax-ho/skill-evolver --skill '*'

Then open a target skill repository that contains SKILL.md and ask Codex to use skill-evolver. Codex runtime resolves the orchestrator and worker skills from the installed collection.

The orchestrator checks whether the skill-evolver CLI is available. If it is missing, the orchestrator attempts to install it from npm:

npm install -g @jaxho/skill-evolver --registry=https://registry.npmjs.org

After the CLI is available, the orchestrator runs the normal loop:

skill-evolver status
skill-evolver init
skill-evolver run

Single-skill Fallback

If you need to install one skill at a time, use the same source with an explicit skill name:

npx --registry=https://registry.npmjs.org skills add jax-ho/skill-evolver --skill skill-evolver
npx --registry=https://registry.npmjs.org skills add jax-ho/skill-evolver --skill skill-evolver-case-builder
npx --registry=https://registry.npmjs.org skills add jax-ho/skill-evolver --skill skill-evolver-answer-runner
npx --registry=https://registry.npmjs.org skills add jax-ho/skill-evolver --skill skill-evolver-answer-judge
npx --registry=https://registry.npmjs.org skills add jax-ho/skill-evolver --skill skill-evolver-gap-analyzer
npx --registry=https://registry.npmjs.org skills add jax-ho/skill-evolver --skill skill-evolver-skill-editor

skill-evolver init initializes project state only; it does not validate worker skill installation paths. Use skill-evolver doctor skills only as a best-effort local file path diagnostic when debugging a local environment.

Local Source Checkout

From this repository:

bun install
bun run build
node dist/cli.js --help

For local source dogfood, prefer installing the public collection first, then testing the built CLI from this checkout.