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

@amirhosseinnouri/claude-skills-sync

v0.1.0

Published

Sync skills installed in ~/.claude into your other Claude Code config directories.

Readme

claude-skills-sync

Sync skills from ~/.claude into your other Claude Code config directories.

The problem

If you run more than one Claude Code account — work, personal, a client — you probably keep them apart with CLAUDE_CONFIG_DIR:

alias claude-personal='CLAUDE_CONFIG_DIR=$HOME/.claude-personal command claude'
alias claude-work='CLAUDE_CONFIG_DIR=$HOME/.claude-work command claude'

Each config directory is fully independent: its own settings, its own history, and its own skills/ folder.

Skill installers don't know about that. bunx skills add …, plugins, and manual clones all write to ~/.claude/skills. So you install a skill, open claude-personal, and the skill isn't there — because that session only reads ~/.claude-personal/skills.

The fix is a symlink per config directory. This CLI does that for you.

Use it

No install needed — run it right after installing a skill:

npx @amirhosseinnouri/claude-skills-sync
bunx @amirhosseinnouri/claude-skills-sync
pnpx @amirhosseinnouri/claude-skills-sync

Or install it once and call it as claude-skills-sync:

npm install -g @amirhosseinnouri/claude-skills-sync
bun install -g @amirhosseinnouri/claude-skills-sync
pnpm add -g @amirhosseinnouri/claude-skills-sync
claude-skills-sync
  1. Pick the skills to sync — the most recently installed one is preselected.
  2. Pick the config directories — every ~/.claude-* folder is found automatically and preselected.
  3. Review the plan, confirm, done.

It creates ~/.claude-<name>/skills/<skill> pointing at the real skill folder, creating skills/ if it doesn't exist yet.

Restart any running Claude session afterwards — skills are read at startup.

Plan symbols

| Symbol | Meaning | | --- | --- | | + | new symlink will be created | | = | already synced, left alone | | ! | something else is already there — replaced only after you confirm |

Options

claude-skills-sync [skill...] [options]

  -a, --all       select every skill in ~/.claude/skills
  -y, --yes       overwrite conflicting entries without asking
  -n, --dry-run   show what would change, write nothing
  -h, --help      show this help

Pass skill names to skip the picker:

claude-skills-sync copywriting pdf

Notes

  • Symlinks point at the skill's resolved path. Skills added by skills add already live in ~/.agents/skills and are symlinked into ~/.claude, so the new link points straight at ~/.agents/skills/<name> instead of chaining through ~/.claude.
  • Nothing is copied and nothing in ~/.claude is modified — updating a skill updates it everywhere.
  • Removing a synced skill is just rm ~/.claude-<name>/skills/<skill>.

Develop

git clone https://github.com/amirhosseinNouri/claude-skills-sync.git
cd claude-skills-sync
bun install
bun run dev       # run from source
bun run build     # bundle with rolldown into dist/
bun link          # put your local build on PATH

License

MIT