Skillshare is live · free · last verified 25 Oct 2026 · viability healthy
Skillshare
Skill sync for AI coding CLIs — one source folder for skills, agents, rules, MCP connections and hooks.
Skillshare earns its place the moment a second coding CLI lands on your machine — that's where hand-copying skills into ~/.claude, ~/.cursor and ~/.codex starts to rot. Merge-mode symlinks mean a sync never clobbers what a tool shipped with, and the install-time audit gate that blocks critical findings unless you pass --force is what separates it from ad-hoc install scripts. Recent 0.25.12 through 0.26.0 releases show steady maintenance rather than a weekend script.
Verdict generatedVerified 5d ago · liveness 76/100 · cite: rightaichoice.com/tools/skillshare
- Developers running two or more AI coding CLIs who want one source of truth for skills and rules
- Teams standardizing prompts, agents, rules and hooks through a shared git remote
- Anyone installing third-party agent skills who wants a blocking audit gate before the install lands
- Power users syncing large skill libraries across machines with plain Git
- Developers who run a single AI CLI and have no plans to add another
- Non-technical users who won't work in a terminal or with git
- Teams that need a hosted skill registry with an admin console instead of git
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Skillshare if you run a single AI coding CLI with no second tool or second machine on the horizon — you'd be layering a sync engine over one tool's own install path.
Skillshare is MIT-licensed and the homepage states "Free and open source," so the cost that actually bites is attention, not license fees: you pay in git remote setup, symlink permissions on Windows, and a few CLI concepts to learn. Compare it against the ongoing cost of prompt drift across tools and teammates.
In short
Skillshare — Skill sync for AI coding CLIs — one source folder for skills, agents, rules, MCP connections and hooks. Best for Developers running two or more AI coding CLIs who want one source of truth for skills and rules, Teams standardizing prompts, agents, rules and hooks through a shared git remote, Anyone installing third-party agent skills who wants a blocking audit gate before the install lands. Free to use.
What is Skillshare?
Skillshare — Skill sync for AI coding CLIs — one source folder for skills, agents, rules, MCP connections and hooks. Best for Developers running two or more AI coding CLIs who want one source of truth for skills and rules, Teams standardizing prompts, agents, rules and hooks through a shared git remote, Anyone installing third-party agent skills who wants a blocking audit gate before the install lands. Free to use.
Skillshare is an open-source setup manager that syncs your AI coding configuration across CLIs. You keep skills, agents, rules, MCP connections, hooks and plugins in one source folder — ~/.config/skillshare/skills/ on macOS/Linux, %AppData%\skillshare\skills\ on Windows — and `skillshare sync` links them into every supported target. The vendor demo shows a single sync landing 14 skills across Claude Code, Cursor, Codex, Gemini and OpenCode at once, with local skills left untouched. Links are per-skill symlinks (NTFS junctions for folders on Windows), so editing a skill at the source shows up immediately in every tool pointing at it. Merge mode is the design choice that earns its keep: a skill a tool already shipped with is never overwritten, and targets you don't use stay untouched. The reverse direction works too — `skillshare collect` pulls a skill born inside one tool back into the shared source. Every install from a GitHub repo or local path hits an audit gate first. Skills are scanned for known injection and exfiltration patterns and destructive commands, and critical findings block the install until you pass an explicit `--force`. Teams get `push` and `pull` over any git remote — GitHub, GitLab, Bitbucket, Azure DevOps, AtomGit, Gitee or self-hosted — plus tracked repos for org-wide skills and a lockfile that records remote skill commits. Recent 0.26.0 releases extend the same model to MCP and hooks: per-Agent MCP `options` blocks stay in source and write only to their own Agent, hook code moves to separate files via `codeFile`, and `mcp serve --http` publishes a skill index any compatible Executor can read. Compared with running each CLI's own install script, the payoff is skills that stop diverging between tools and between people. MIT-licensed and local-first — git is the sharing layer, not a hosted dashboard.
Key features
- Sync skills, agents, rules, MCP connections, hooks and plugins from one source directory into 76+ AI coding CLIs
- Per-skill symlinks (NTFS junctions for folders on Windows) so source edits propagate immediately
- Merge sync mode that never overwrites a skill the tool already had
- `skillshare collect` pulls a skill created inside one tool back to the shared source
- Install-time audit gate scanning skills for prompt injection, exfiltration patterns and destructive commands
- Critical audit findings block an install until you pass an explicit `--force`
- Project mode with `.skillshare/skills/` that auto-activates when you cd into a project
- Tracked repos for org-wide skills, with remote skill commits recorded in a lockfile
- `skillshare push` and `pull` over any git remote: GitHub, GitLab, Bitbucket, Azure DevOps, AtomGit, Gitee or self-hosted
- Git tokens stored in a host-scoped credential helper so `ps` no longer exposes them (0.25.12)
- `update --all` skips unchanged skills and reports sanitized errors on unfetchable repos (0.25.12)
- MCP agents edit listed skills via revision-locked `preview_skill_edit` and `apply_skill_edit` (0.25.13)
- Per-agent MCP `options` blocks kept in source and written only to their own Agent (0.26.0)
- Hook code in separate files via `codeFile` or `{from: path}` instead of inline YAML (0.26.0)
- `mcp serve --http` publishes `/.well-known/agent-skills/index.json` for Executor skill loading (0.26.0)
Behind the verdict
Most people come to Skillshare because they've already felt the pain: a good skill written for Claude Code, then manually pasted into Cursor, then re-pasted after a Codex update wiped it. One source folder plus `sync` ends that loop. We'd reach for it the day you install a second CLI, not before — a single-tool user gets little from the indirection. The feature that actually changes behavior is merge mode. Because a sync never overwrites a skill a target already had, you can run it casually without reading the dry run first. That's rare for a config tool, and it's the reason the per-skill symlink approach is worth the complexity over plain copy scripts. The audit gate is the other one. Installing third-party agent skills from a random GitHub repo is a real supply-chain risk, and having critical injection or exfiltration findings block the install until you pass `--force` puts a speed bump exactly where it belongs. Teams should treat it as a floor, not a full security review. Where it bites: this is a terminal-first tool. The desktop app and vendor documentation soften the on-ramp, but you'll still be working with git remotes and folder layouts. Environments that forbid symlinks or junctions on shared or networked folders will fight it. Compared with a hosted skill registry, Skillshare trades an admin console for plain git. If your team already lives in GitHub, that's a feature — review, history and access control come free. If you want a browser UI to browse and approve skills, it isn't that. Pick it for teams that would rather own their config than rent a dashboard.
Limitations
- Skillshare is a setup manager, not a model: it syncs skills, agents, rules, MCP connections and hooks into targets and does not write skills for you.
- The audit is static analysis of skill text matched against known injection and exfiltration patterns — it is not a sandbox, and execution permissions remain with your AI tools.
- Skills live as Markdown files in one source folder synced via per-skill symlinks, so a working folder is a prerequisite, and on Windows single-file symlinks need Developer Mode or degrade to copies.
- Cross-machine sharing assumes a git remote and comfort with push and pull, though the desktop app and `skillshare ui` cover GUI use.
as of 2026-10-20
Researching Skillshare? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Skillshare still active?
Skillshare is live · free · last verified 25 Oct 2026 · viability healthy.
Viability score
How well maintained and how widely used is Skillshare? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →What's new in Skillshare
Checked 10 days agoAcross the latest 3 updates: 2 feature updates and 1 changelog entry.
[0.26.0] Per-Agent MCP options, hook code files, and an Executor-readable skill index
MCP servers keep per-Agent options in source and write each block only to its Agent. Hooks can keep code in separate files via codeFile. `mcp serve --http` publishes /.well-known/agent-skills/index.json for Executor.
[0.25.13] Edit skills over mcp serve with preview and audit
Skills listed in mcp.serve.edit.skills can be changed one file at a time via revision-locked preview_skill_edit and apply_skill_edit. Each save is audited; edits cannot create, delete or rename files.
[0.25.12] Git tokens no longer show up in ps; update skips unchanged skills
Git now gets the token from a host-scoped credential helper, keeping it out of the process list during clones and fetches. `update --all` skips unchanged skills and sanitizes errors from unfetchable repos.
What do users say about Skillshare?
What people actually say about Skillshare — is it worth it?
Our community sentiment research written Jul 30, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about Skillshare— pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 25 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.
Verification history
We have re-verified Skillshare 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed summary, our verdict, integrations, who should skip it, description, features, who it suits, pricing tiers
- — changed limitations, pricing page
- — changed pricing fit, summary, features, use cases, who it suits, who should skip it, integrations, pricing tiers, setup time, switching out, limitations, our verdict, description, switching in
- — changed who it suits, who should skip it, description, pricing tiers, summary, our verdict, features, integrations
- — changed pricing page
- — changed SSL certificate, who it suits, who should skip it, features, pricing tiers, integrations, our verdict, summary, description
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Skillshare cost in 2026?
Skillshare: Free to use. Pricing last verified 25 Oct 2026.
Plans compared
Every published Skillshare tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Open Source | Free | — | Developers running two or more AI coding CLIs, and teams sharing skills through a git remote, who want local-first management with no hosted dependency.Adds: Starting tier: MIT-licensed CLI and desktop app, sync to all supported CLIs, merge-mode sync, install-time audit gate, git push and pull, and the `skillshare ui` local dashboard. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Skillshare's pricing actually pencils out — and where peers do it cheaper.
Skillshare is MIT-licensed and the homepage states "Free and open source," so the cost that actually bites is attention, not license fees: you pay in git remote setup, symlink permissions on Windows, and a few CLI concepts to learn. Compare it against the ongoing cost of prompt drift across tools and teammates.
Has Skillshare's pricing changed?
No plan price for Skillshare has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Skillshare?
Pick Skillshare if you are Developers running two or more AI coding CLIs who want one source of truth for skills and rules, Teams standardizing prompts, agents, rules and hooks through a shared git remote, Anyone installing third-party agent skills who wants a blocking audit gate before the install lands, Power users syncing large skill libraries across machines with plain Git.
Look elsewhere if you are Developers who run a single AI CLI and have no plans to add another, Non-technical users who won't work in a terminal or with git, Teams that need a hosted skill registry with an admin console instead of git, Environments that forbid symlinks or junctions on shared or networked folders.
Skip it if Skip Skillshare if you run a single AI coding CLI with no second tool or second machine on the horizon — you'd be layering a sync engine over one tool's own install path.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Skillshare actually fits — and what changes day-one when you adopt it.
You already have skills in Claude Code and Cursor and just added Codex. You move everything into ~/.config/skillshare/skills/, run `skillshare init` to auto-detect the CLIs, then `skillshare sync`.
Outcome: The demo output shows all three targets merged with 14 skills linked, and skills each tool shipped with stay intact because merge mode never overwrites them.
You put shared rules in a tracked repo and commit project config with `.skillshare/skills/` alongside the code. A new teammate clones the repo, runs `skillshare install -p` and `skillshare sync -p`.
Outcome: Everyone's Claude Code and Codex behave the same on the legacy API checklist, and remote skill commits are recorded in a lockfile instead of being copied out of chat.
You find a skill repo and run `skillshare install <owner/repo>`. The audit gate scans it for injection, exfiltration and destructive commands before anything lands in source.
Outcome: Critical findings block the install; you review the findings and only pass `--force` if you accept them. Once installed, it syncs to targets on the next `sync`.
Use cases
- Sync a library of AI coding skills and rules across Claude Code, Cursor, Codex and Pi with one `skillshare sync`
- Standardize AI assistant behavior for a team by keeping org-wide skills in a tracked git repository
- Audit a third-party skill for prompt injection or exfiltration before it reaches any agent
- Keep a code-review checklist in `.skillshare/skills/` so a Claude Code user and a Codex user on the same repo share it
- Collect a skill you wrote inside one CLI back to your central source with `skillshare collect`
- Keep the same skill folder on a laptop and a desktop with `skillshare push` and `skillshare pull`
- Let an MCP agent propose skill edits through revision-locked preview-and-apply instead of hand-offs
- Browse and install skills from a local dashboard with `skillshare ui` rather than the terminal
Setup time & first value
How long it actually takes to get something useful out of Skillshare — broken out by persona, not the marketing-page minute.
CLI path: about five minutes to first sync — run the install script, `skillshare init` to auto-detect CLIs, one `skillshare install`, one `skillshare sync`. Desktop app: first launch walks you through CLI setup, tool selection and the first sync. Wanting to look first? The Docker Playground is one command with no local install.
Switching to or from Skillshare
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From hand-copied per-CLI folders: use the "From Existing Skills" guide to migrate and consolidate existing skills into the shared source, then sync
- →From a single CLI's own install script: move skills into ~/.config/skillshare/skills/, run `skillshare init` to auto-detect targets, then `skillshare sync`
- →From a team chat thread of instructions: put the checklist in `.skillshare/skills/`, commit the project config, and teammates run `skillshare install -p` plus `skillshare sync -p`
- →From Docker Playground trial: clone the repo, run `make playground` to evaluate, then switch to the real installer (`curl -fsSL .../install.sh | sh`) for daily use
- ↗To a single tool's native skill folder: disable the other targets, then copy the source skills into that tool's own directory and stop running sync
- ↗To a hosted skill registry: export the Markdown files from the source folder and import them into the registry; Skillshare's git remote is the sharing layer, not a hosted console
- ↗To plain git dotfiles: add the source folder to your dotfiles repo and replace `skillshare sync` with your existing symlink or stow setup
Integrations
Resources & guides
- Documentationskillshare.runkids.cc
Docs · Skillshare
Full product docs from skillshare.runkids.cc
- Quickstartskillshare.runkids.cc
First Sync · Skillshare
Get up and running fast from skillshare.runkids.cc
- Quickstartskillshare.runkids.cc
Desktop App · Skillshare
Get up and running fast from skillshare.runkids.cc
- Quickstartskillshare.runkids.cc
From Existing Skills · Skillshare
Get up and running fast from skillshare.runkids.cc
- API Referenceskillshare.runkids.cc
Commands · Skillshare
Methods, params, types from skillshare.runkids.cc
- Documentationskillshare.runkids.cc
Troubleshooting · Skillshare
Full product docs from skillshare.runkids.cc
- Resourceskillshare.runkids.cc
Llms Full · Skillshare
Helpful link from skillshare.runkids.cc
Tutorials & Learning
YouTube returned 6 videos for “Skillshare”, and we withheld 6: 6 could not be judged, because “Skillshare” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Skillshare.
Official links
What are the best Skillshare alternatives?
The closest alternatives to Skillshare we list are Taste Skill, Maestro and Ui Ux Pro Max Skill. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Taste Skill | Free | Free | — |
| Maestro | Freemium | Pricing not published | — |
| Ui Ux Pro Max Skill | Free | Free | — |
Alternatives to Skillshare
View all
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
Maestro
Open-source MCP skill that adds 25 workflow commands, persistent memory, and an audit trail to the AI coding agents you already run
Ui Ux Pro Max Skill
Free open-source design-intelligence skill that feeds UI styles, palettes, fonts, and chart rules into Claude Code, Cursor, and other AI coding assistants.
Tools that pair well with Skillshare
Common stack mates teams adopt alongside Skillshare, with the specific reason each pairing earns its keep.
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
Maestro
Open-source MCP skill that adds 25 workflow commands, persistent memory, and an audit trail to the AI coding agents you already run
Ui Ux Pro Max Skill
Free open-source design-intelligence skill that feeds UI styles, palettes, fonts, and chart rules into Claude Code, Cursor, and other AI coding assistants.
Skillshare vs its closest rival
Skillshare's closest head-to-head is with Spider Cloud — These two tools shouldn't be on the same shortlist. Skillshare is a free, open-source CLI that syncs skill files and rules across coding agents like Claude Code, Cursor, and Codex — it solves a workflow-consistency problem for developers using multiple agent CLIs. Spider Cloud is a paid API that renders, crawls, and searches the web, returning markdown or structured JSON for agents and RAG pipelines, with residential proxy and AI extraction costs on top of request pricing. If your problem is 'my agents have different skill libraries,' pick Skillshare. If your problem is 'my pipeline needs live web pages,' pick Spider Cloud — but you're not choosing one over the other. Verdict generated
Head-to-head comparisons
Skillshare vs Spider Cloud
These two tools shouldn't be on the same shortlist. Skillshare is a free, open-source CLI that syncs skill files and rules across coding agents like Claude Code, Cursor, and Codex — it solves a workflow-consistency problem for developers using multiple agent CLIs. Spider Cloud is a paid API that renders, crawls, and searches the web, returning markdown or structured JSON for agents and RAG pipelines, with residential proxy and AI extraction costs on top of request pricing. If your problem is 'my agents have different skill libraries,' pick Skillshare. If your problem is 'my pipeline needs live web pages,' pick Spider Cloud — but you're not choosing one over the other.
GeneratedSkillshare vs Dbos
If you manage skills across multiple AI CLIs, Skillshare is a no-brainer free tool to unify your prompts and rules. For building resilient, stateful AI workflows on Postgres with durable execution and human-in-the-loop, DBOS is the clear winner. They solve entirely different problems—choose based on whether you need skill sync or workflow orchestration.
GeneratedSkillshare vs Voyage Ai
These aren't competitors, so there's no head-to-head to call: pick Skillshare if you're a developer juggling multiple AI coding CLIs and want free, open-source sync plus a prompt-injection audit across Claude Code, Cursor, Codex and friends. Buy Voyage AI if your problem is retrieval accuracy — domain-tuned embeddings and rerankers for finance, legal, code or multimodal RAG, priced by sales conversation. A buyer with budget and a problem would never shortlist both, because one is a terminal tool and the other is a retrieval layer inside your stack.
GeneratedSkillshare vs Temporal Ai
If you're a developer juggling multiple AI CLI tools and need to keep skills (prompts, rules) in sync, Skillshare is a lightweight, free, open-source solution. But if you're building production-grade AI agents or workflows that must survive crashes, retries, and human oversight, Temporal AI's durable execution platform is the enterprise-grade choice—though it introduces complexity. Pick Skillshare for skill management, Temporal for workflow resilience.
GeneratedSkillshare vs Bito
If you're a solo dev or power user juggling multiple AI CLI tools and want to keep skills consistent without paying, Skillshare is the no-brainer. For engineering teams grappling with multi-repo complexity, cross-repo dependencies, and scaling AI agent context across the entire SDLC — from design to code review to issue triage — Bito's knowledge graph and enterprise integrations justify its contact-sales pricing. Choose based on team size and repository scale.
GeneratedFrequently asked questions
Categories
Best-of guides
Used Skillshare? Help shape our editorial sentiment research.