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

stan-skills

v0.1.5

Published

Bootstrap Claude Code configuration in any repository: install the plugins, skills, and commands you want, declaratively and reproducibly.

Readme

stan-skills

Bootstrap Claude Code configuration in any repository: select the plugins you want, and get a reproducible, auditable .claude/settings.json plus a stan-skills.json manifest — instead of clicking through /plugin by hand on every clone.

stan-skills writes exactly two keys — extraKnownMarketplaces and enabledPlugins — into a target repo's .claude/settings.json, selecting from a built-in catalog of Stan's own plugins (premortem, security-check, logo-concept, saas-challenge, published from the stan marketplace) plus popular third-party plugins (frontend-design, code-simplifier, claude-md-management, mattpocock-skills, modern-web-guidance).

Usage

npx stan-skills install

This opens an interactive selection prompt, pre-checking plugins based on detected signals in the target repo (framework, tsconfig.json, backend dependencies, presence of CLAUDE.md, …). Every pre-check shows its reason and can be unchecked.

Non-interactive usage:

stan-skills install --preset frontend --yes
stan-skills install --preset frontend --dry-run   # preview only, writes nothing

Commands

| Command | Effect | |---|---| | stan-skills / install | select, then write configuration | | add <id...> | add plugins without the TUI | | remove <id...> | remove plugins | | list [--available] | current state, or the full catalog | | sync | realign settings.json with the manifest | | doctor | diagnose drift, never writes |

Options

| Option | Effect | |---|---| | --preset <name> | non-interactive selection: minimal, frontend, backend, product, full | | --yes / -y | accept the pre-selected plugins without the TUI | | --dry-run | print the diff, write nothing | | --scope <s> | project (default) · local · user | | --cwd <path> | target repository | | --no-detect | disable automatic stack detection | | --json | machine-readable output (list, doctor) |

What gets written

Two files, both meant to be committed:

  • .claude/settings.json — what Claude Code reads. stan-skills only ever touches extraKnownMarketplaces and enabledPlugins; every other key (model, permissions, statusLine, …) is preserved untouched.
  • stan-skills.json — what you asked for: the preset, the resolved plugin list, and a checklist of interactive setup steps (see below).

After writing settings.json, install and add also run claude plugin install <id> --scope <scope> for every newly-enabled plugin, so the plugin is actually installed, not just marked enabled. If the claude CLI isn't on PATH, or a specific install fails, that plugin is listed in the printed checklist instead so you can run it by hand.

A note on trust prompts

Committing enabledPlugins means that when a teammate opens the repo, Claude Code will ask them to trust each new marketplace on first start. That prompt is expected, not a bug — a third-party marketplace runs code, and stan-skills does not attempt to bypass that confirmation.

Interactive setup steps

Some plugins need a one-time interactive setup (/setup-matt-pocock-skills) or a missing CLAUDE.md. stan-skills cannot run these for you — they need human answers — so it prints them as a checklist and tracks their status in stan-skills.json. Check on them anytime with stan-skills doctor.

Requirements

Node ≥ 22.12.

Source

github.com/57H07/AI-Skills (this package lives in the cli/ subdirectory).

License

MIT