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

@papi-ai/skills

v0.1.0

Published

PAPI's shareable Claude Code skill bundle — single source of truth, installed (not copied) into projects with pinned versioning

Readme

@papi-ai/skills

The canonical, versioned bundle of PAPI's shareable Claude Code skills. Projects install this package instead of copying skill files, so they pick up fixes by bumping a pinned version rather than silently drifting from forked copies.

What's in the bundle

Nine ship-ready skills (the PAPI-internal skills — bootstrap-project, friction-promote, patch-notes, support-debug — are intentionally not shipped):

Generic engineering (eager): check-mcp, pr-reviewer, deployment-completeness-audit, playwright-skill

Cycle methodology (lazy / trigger-loaded): papi-plan, papi-build, papi-idea, papi-strategy, papi-advanced

The authoritative inventory + checksums live in manifest.json, regenerated from the skill content on prepack.

Install into a project

npx @papi-ai/skills install /path/to/project        # symlink (copy fallback)
npx @papi-ai/skills install /path/to/project --copy  # force copy, no symlinks
npx @papi-ai/skills install /path/to/project --force # overwrite a diverged skill

Each packaged skill is symlinked into <project>/.claude/skills/<name>. Where symlinks are unsupported (some Windows / restricted filesystems) it copies instead.

Pinned versioning

Published as @papi-ai/[email protected]. A project pinned to 0.1.0 keeps that exact content when 0.2.0 ships — upgrades are explicit (npm i @papi-ai/skills@latest then re-run the installer), never silent.

Local overrides

A skill placed in <project>/.claude/skills.local/<name> is an intentional override: the installer never touches it and PAPI's stale-fork detection never flags it. Use this to customise a skill without fighting the package.

Stale-fork detection

orient (with deep_housekeeping: true) compares the project's .claude/skills/ against this manifest and surfaces any skill whose content has diverged from the pinned registry, offering replacement. It prompts — it never auto-overwrites.

import { detectStaleForks } from '@papi-ai/skills/manifest';
const forks = detectStaleForks('/path/to/project'); // [{ name, packagedChecksum, localChecksum }]