skills-hub: One Skill Library, Synced Across 47 Coding Tools

Install the same skill in Claude Code, then Codex, then Cursor, and you now have three diverging copies, three update sources, and no idea which one is current. skills-hub (Skills Hub) is a cross-platform desktop app — Tauri and React — that flips the model: "Install once, sync everywhere".

Why This Skill Matters

Every AI coding tool grows its own skills directory and install flow, and hand-maintaining them gets messy fast: the same skill copied many times, unclear where updates come from, enabled states drifting between tools, bulk cleanup eating an afternoon. Skills Hub installs skills into one central repository (defaulting to ~/.skillshub) and syncs them out to your tools from there. It prefers symlink/junction links and automatically falls back to copy when a system restricts symlinks.

The app ships 47 built-in tool adapters — the README's table covers Claude Code (~/.claude/skills), Codex (~/.codex/skills), Cursor (~/.cursor/skills), OpenCode, Antigravity, Gemini CLI, and dozens more — and supports adding custom skills directories for internal tools.

Installation

Skills Hub is a desktop app, not an npm package. The project publishes prebuilt binaries on its GitHub Releases page — as of v0.9.1, macOS DMGs for Apple Silicon and Intel plus Windows installers for x64 and ARM64. The README marks both Windows and Linux as expected by design but not validated locally, so check the latest release before relying on either.

To run it from source instead, you need Node.js 18+ (20+ recommended), a stable Rust toolchain, and Tauri's system dependencies:

npm install
npm run tauri:dev

One macOS note from the README: on unsigned or non-notarized builds, Gatekeeper may report the app as "damaged" or from an unverified developer. The documented fix is xattr -cr "/Applications/Skills Hub.app".

Real Workflow: Consolidate Skills Scattered Across Tools

1. Import what you already have. Skills Hub scans installed tool directories for importable skills — only folders containing a SKILL.md qualify — and the discovery banner lets you review and pull them into the central library. Scan sources are configured separately from sync targets and persist across restarts.

2. Install new skills from anywhere. Explore aggregates curated skill lists and online search; Add Skill takes a local folder or a Git repository. Before installing, you assign tags, choose global or project scope, and pick which tools to sync to.

3. Let it sync. The skill is stored once in ~/.skillshub and synced into each tool's directory according to that tool's rules — project-scope skills go to paths like <project>/.claude/skills or <project>/.agents/skills.

4. Manage in bulk. My Skills shows card and list views with each skill's source, tags, sync scope, target tools, and enabled state. Select many at once and apply tags, tool targets, enable/disable, or deletion in one action.

5. Keep them current. Updates can register a system-level schedule that refreshes Git and local-source skills even while the app is closed, then re-syncs to your configured tool targets. The last run reports checked, updated, and failed counts.

A second workflow worth knowing: project-level sync. The skill stays stored once in the central library, but its sync target is one project's skills directory — handy when a skill only makes sense inside a specific repo and you do not want it in every tool's global path.

Tips

• Disabling a skill is not deleting. Disable only removes the tool-side sync; the skill and its configuration stay in the central library and can be re-enabled later.
• Do not panic at TARGET_EXISTS. The default is non-destructive: an existing target folder is not overwritten. Remove it or retry through the overwrite flow.
• Cursor sync is always copy. Cursor does not support symlink-based skill directories, so Skills Hub forces a directory copy for that target.
• Internal or wrapped agents with their own skills directories can be added in Management Center as custom tool targets.
• Tags organize, nothing more. The README notes tags help you find and group skills — they do not change where a skill syncs or which tools can use it.

When Not to Use This

If you use a single coding tool, its own installer is simpler than a whole sync layer. And if your OS restricts symlinks — the README calls out Windows especially — the automatic fallback to directory copy removes the single-copy guarantee that motivates the tool, so weigh whether the trade still pays. The README also marks Windows and Linux as unvalidated platforms, while macOS is the one it has verified.

See the leaderboard for more skills.