Skip to main content

skillshare vs. vercel/skills — When to Use Which

· 3 min read
runkids
runkids
Creator of skillshare

vercel/skills and skillshare are both CLI tools for managing AI coding skills across multiple agents. If you're choosing between them — or considering a migration — here's an honest comparison.

What They Have in Common​

Both tools solve the same core problem: managing AI skill files across 40+ coding agents (Claude Code, Cursor, Codex, etc.). Both offer:

  • Install skills from Git repositories
  • Sync to multiple AI tool targets
  • Support for symlink and copy modes
  • Project-level and global skill management

Where vercel/skills Shines​

Best for quick, curated installs:

  • Runs via npx skills — no binary installation needed if you have Node.js
  • Curated skill discovery via npx skills find with interactive selection
  • Strong Vercel/Next.js ecosystem integration
  • Familiar npm-based workflow for JavaScript developers

Use vercel/skills when:

  • You're already in the Node.js ecosystem
  • All your skill repos are on GitHub (it currently only supports GitHub)
  • You want a curated, community-driven skill catalog
  • You prefer npx-based tooling with no permanent install
  • Your workflow is primarily single-machine, single-project

Where skillshare Shines​

Best for multi-tool sync, multi-platform, and team workflows:

  • Single binary — no Node.js, npm, or runtime dependencies
  • Any Git host — GitHub, GitLab, Bitbucket, Gitea, Azure DevOps, AtomGit, Codeberg, self-hosted, and any HTTPS/SSH git server
  • Bidirectional sync: collect skills from targets back to source
  • Cross-machine sync via push/pull
  • Built-in security audit (15+ detection patterns, auto-block on install)
  • Backup/restore with timestamped snapshots
  • Web dashboard (skillshare ui)
  • Organization-wide skill distribution via tracked repos
  • Works offline (core operations need no network)

Use skillshare when:

  • You use multiple AI tools and need one source of truth
  • Your skills live on GitLab, Bitbucket, Azure DevOps, or self-hosted Git — not just GitHub
  • You work across multiple machines
  • Your team needs standardized skills via git
  • You need security scanning for untrusted skill sources
  • You want zero runtime dependencies (CI/CD, Docker, air-gapped environments)

Feature Comparison​

Featurevercel/skillsskillshare
Install methodnpx (Node.js)Single binary
Git platform supportGitHub onlyGitHub, GitLab, Bitbucket, Gitea, GHE, Azure DevOps, AtomGit, Codeberg, any HTTPS/SSH host
Sync modesSymlink, copyMerge (per-skill symlink), symlink, copy
Multi-tool syncYesYes
Collect (target → source)NoYes
Cross-machine syncNoYes (push/pull)
Security auditNoYes (15+ patterns)
Backup/restoreNoYes
Web UINoYes
Hub/registryCommunity catalogSelf-hosted hub index
Offline operationNeeds npmYes (core operations)
Project skillsYesYes

Migrating from vercel/skills​

If you decide to switch, the process is straightforward:

Step 1: Install skillshare​

curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh
skillshare init

Step 2: Collect existing skills​

If vercel/skills already synced skills to your AI tool directories:

skillshare collect

This copies skills from your target directories into skillshare's source.

Step 3: Sync​

skillshare sync

Step 4: Ongoing updates​

skillshare check          # Detect upstream changes
skillshare update --all   # Apply updates
skillshare sync           # Push to all tools

Can They Coexist?​

Yes. Both tools use symlinks (or copies) to the same target directories. However, running both simultaneously on the same targets may cause conflicts — one tool's symlinks may be overwritten by the other. If you're evaluating both, use them on separate targets or test one at a time.

Resources​