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

skreg-cli

v0.2.1

Published

A command line tool for manging AI skills which are verified and trusted

Readme

skreg

A package registry for AI coding assistant skills, built on cryptographic publisher identity and trust.

What is skreg?

skreg is a registry for skills — reusable instruction sets that extend what your AI coding assistant can do. Think of it like npm or crates.io, but for prompts you share across projects and teams.

Browse and install community skills from skreg.ai. Package your own with a single command and publish them for others to use — or run a private registry your team controls.

Trust & Verification

Every package published to skreg carries a cryptographic publisher signature. Two verification tiers are supported:

| Tier | Badge | How | |------|-------|-----| | Self-signed | ◈ self-signed | Publisher generated their own key. Key consistency is enforced at the namespace level — once a key is used it cannot be swapped without an explicit rotation. | | CA-verified | ✦ verified | Publisher obtained a CA-issued cert from the skreg Publisher CA. Proves organisation identity. |

All packages — regardless of tier — pass content, safety, and structure vetting before appearing in search. The registry does not counter-sign packages; only the publisher's key appears in the signature.

Key material is stored in ~/.skreg/keys/ with chmod 700. Run skreg certify to obtain a CA-verified cert. Run skreg rotate to safely rotate your namespace's signing key.

Install

Pre-built binary (macOS and Linux)

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/dymocaptin/skreg/releases/download/v0.1.2/skreg-cli-installer.sh | sh

Homebrew (macOS and Linux)

brew tap dymocaptin/tap
brew install skreg-cli

npm

npm install -g skreg-cli

cargo (build from source)

Requires Rust (rustup.rs).

git clone https://github.com/dymocaptin/skreg.git
cargo install --path skreg/crates/skreg-cli

After installing with any method, verify with:

skreg --version

Using skills

Finding a skill

Browse and search for skills at skreg.ai.

Coming soon: skreg search <query> — find skills directly from the CLI.

Installing a skill

skreg install <namespace>/<name>

For example:

skreg install dymocaptin/color-analysis

Skills are installed to ~/.skreg/packages/ and are available to your AI coding assistant automatically.

Using an installed skill

Coming soon: Native Claude Code integration — skills installed via skreg will be available directly through the Claude Code plugin marketplace.

Building skills

Anatomy of a skill

A skill is a directory with two files:

my-skill/
├── SKILL.md        # The skill prompt and instructions
└── manifest.json   # Metadata

SKILL.md starts with a YAML frontmatter block followed by the instructions your AI assistant will follow when the skill is active:

---
name: color-analysis
description: Analyzes the dominant colors in any image file, producing a ranked
             color palette with hex codes, RGB/HSL values, human-readable color
             names, and percentage breakdowns.
---

# Color Analysis

You are an expert color analyst. When the user provides an image, analyze it
and produce a detailed color palette report.
...

manifest.json declares the package identity:

{
  "namespace": "dymocaptin",
  "name": "color-analysis",
  "version": "1.0.0",
  "description": "Analyzes the dominant colors in any image file, producing a ranked color palette with hex codes, RGB/HSL values, human-readable color names, and percentage breakdowns."
}

Packaging

From inside your skill directory, run:

skreg pack

This produces a <name>-<version>.skill archive ready to publish.

Publishing

First, log in to your registry:

skreg login <your-namespace>

Then publish:

skreg publish

skreg will pack, upload, and vet your skill. Once it passes review it appears on skreg.ai.

Self-hosting

You can run your own skreg registry. Deploy the infrastructure with Pulumi, then point the CLI at your domain:

skreg login <your-namespace> --registry https://registry.example.com

See infra/README.md for the full deployment guide.

Contributing

skreg is open source. See CONTRIBUTING.md for how to build from source, run tests, and submit changes.

License

Apache 2.0 — see LICENSE.