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

skillsync-cli

v0.1.0

Published

Install AI agent skills once, use them in any project, across any provider.

Downloads

3

Readme

skill-sync

Install AI agent skills once, use them in any project, across any provider.

The Problem

When using AI coding assistants like Cursor, Claude, or OpenCode, each expects skills in different directories. Without skill-sync:

  • You copy the same skills into every project
  • Skills get out of sync across projects
  • Updating means manually updating each copy
  • Disk space wasted on duplicate files

The Solution

skill-sync downloads skills once to a global store and creates symlinks to your projects. One copy, used everywhere, updated in one place.

Install

npm install -g skillsync-cli

Quick Start

cd my-project
sks init                              # Create .skillsync.yaml
sks install vercel-labs/agent-skills  # Download skill + link to providers

In another project that needs the same skill:

cd another-project
sks init
sks install                           # Select from global store (no download)

Commands

| Command | Description | | ---------------------- | ----------------------------------------------------------------- | | sks init | Create .skillsync.yaml config file in the current project | | sks install <source> | Download skill via npx add-skill and link to selected providers | | sks install | Browse skills already in global store and link to providers | | sks update | Re-fetch all configured skills from their sources | | sks update <skill> | Re-fetch a specific skill | | sks sync | Recreate all symlinks (useful after cloning a repo) | | sks list | Show configured skills and their symlink status |

How It Works

~/.skillsync/skills/                     ← Global store (skills downloaded here)
├── react-best-practices/
└── typescript-patterns/

project-a/
├── .skillsync.yaml                      ← Tracks skills + providers for this project
├── .cursor/skills/react-best-practices  → symlink to global store
└── .opencode/skill/react-best-practices → symlink to global store

project-b/
├── .skillsync.yaml
└── .claude/skills/react-best-practices  → symlink to global store

Both projects share the same skill files. Run sks update once, and all projects get the latest version automatically.

Supported Providers

| Provider | Skills Directory | | ----------- | ----------------- | | Cursor | .cursor/skills | | OpenCode | .opencode/skill | | Claude | .claude/skills | | Codex | .codex/skills | | Amp | .agents/skills | | Antigravity | .agent/skills |

Config File

Each project has a .skillsync.yaml that tracks its skills:

skills:
  - name: react-best-practices
    source: vercel-labs/agent-skills
    providers:
      - cursor
      - opencode

  - name: auth-patterns
    source: better-auth/skills
    providers:
      - cursor
      - claude

Commit this file so teammates can run sks sync to set up their environment.

Workflow

First time setup:

sks init
sks install vercel-labs/agent-skills
# → Downloads to ~/.skillsync/skills/
# → Prompts: select providers
# → Creates symlinks

New project, same skills:

sks init
sks install
# → Shows skills in global store
# → Select what you need
# → No download, just symlinks

Keep skills updated:

sks update
# → Re-runs add-skill for each source
# → All projects automatically updated via symlinks

Clone a repo with .skillsync.yaml:

git clone repo && cd repo
sks sync
# → Creates symlinks based on config