Files
Willie 68a3f52c9d docs(comparison): mention check --exit-code in the Updates row
The row says skills check exits 1 on updates or local changes, while the Skillshare cell listed only check and update, which reads as if Skillshare cannot gate CI on drift. check --exit-code (#865) does that.
2026-11-12 00:37:28 +08:00

6.3 KiB

sidebar_position
sidebar_position
9

Comparing Skill Management Approaches

Both Vercel's npx skills and Skillshare manage skills across multiple AI tools. The difference is not “one installs, the other syncs.” Choose by what you need to manage: skills, or a broader AI working environment.

This comparison uses the published skills v1.8.1 package metadata and its official CLI reference. Experimental commands may change or disappear; this is a versioned comparison, not a claim about every installer.

Architecture at a Glance

npx skills: Skill discovery and management

skills.sh provides a discovery entry point. The CLI supports multiple agents, project and global installation, symlinks to a canonical copy or independent copies, update checks, and updates. Agent selection and confirmation can be supplied through flags; interactive prompts are not mandatory.

It also records installed skills in lock files. Its experimental commands support project restoration and npm-based synchronization, so it is not accurate to describe it as stateless or install-only.

Skillshare: A managed environment across tools

Skillshare keeps source resources and target configuration separate, then synchronizes them to your tools. Beyond skills, it manages agent definitions, rules and other extras, MCP connection settings, and native hooks for supported clients. A local Web dashboard provides a visual management interface.

The useful distinction is managing these resources together across tools, machines, and team workflows—not exclusive ownership of symlinks or multi-agent installation. Resource formats and client capabilities still differ; not every resource works in every tool.

Feature Comparison

Capability npx skills v1.8.1 Skillshare
Discovery skills.sh and skills find CLI search and local Web dashboard
Multiple agents and scopes Multiple agents; project and global installs Configured targets; project and global modes
Shared skill files Symlinks to a canonical copy; copy option Source directory with merge, copy, or directory-symlink modes
Updates skills check (exits 1 on updates or local changes) and skills update skillshare check (add --exit-code to exit 1 when anything is not up to date) and skillshare update
Project restoration Experimental skills experimental_install (or skills install with no source) restores supported sources from skills-lock.json Declarative skill configuration and source resources; see manifest
npm project sync Experimental skills experimental_sync reads installed dependencies and package.json skill declarations Source-to-target synchronization; not the same npm dependency workflow
Cross-machine workflow Project lock restoration and npm sync can help rebuild project skills Git-backed push / pull, scoped by git_root
Beyond skills The cited CLI reference focuses on skills Agent definitions, extras such as rules, MCP settings, and hooks for supported clients
Local management and recovery The cited CLI reference does not document a local dashboard or target-backup commands skillshare ui, target backups and restore, plus managed-file recovery
Runtime Node.js and npm/npx Go binary; Git required for Git-backed operations

What the experimental commands cover

  • experimental_install (also run as skills install with no source) restores supported lock entries into .agents/skills/ and links them into agent directories (copies for skills recorded in copy mode): those given with --agent, otherwise the agents last selected, otherwise the agents it detects. It does not install npm dependencies. Installed skills whose files match the lock's content hash are not fetched again and only get the agent links they are missing; skills whose files differ are restored from their source, and --force reinstalls every skill. Frozen-lock mode checks content hashes and is the default in CI.
  • experimental_sync links skills shipped by installed npm dependencies and resolves skill declarations in package.json. It tracks these in skills-lock.json, removes skills no longer provided, and preserves separately added skills. Copies require another sync after dependency updates.

These are real synchronization and restoration capabilities, but they are not a backup of an entire AI tool configuration.

Choosing the Right Tool

Stay with npx skills if you mainly want to discover, install, and update public or private skills—even across several agents. It is also a reasonable fit when you want skills to follow npm project dependencies and accept the experimental status of that workflow.

Choose Skillshare when the problem extends beyond installing skills: “I use Claude Code and Codex, and I want to carry my managed skills, rules, MCP settings, and supported hooks to another machine.” Its source/target configuration, Git workflows, local dashboard, and recovery tools address that broader management job.

Portability still needs setup: choose the Git scope, configure targets on the destination, and provision credentials and external dependencies separately. push defaults to the skills source; it does not automatically publish all configuration or back up the whole machine. See Git root scope and sync.

Migrating to Skillshare

You do not need to replace a working installer immediately. Move only the resources you want Skillshare to own, and avoid having both tools update or remove the same managed skill.

Migration is not currently a lossless lock import: collected skills are local copies without the original repository tracking. Reinstall from the recorded source if you need subsequent Skillshare updates. Back up and preview before handing over ownership; follow the npx skills migration guide rather than treating collection alone as a complete migration.

See Also