* fix(install): keep a moved skill's record instead of reinstalling it Install records are keyed by path, so a skill moved with mv shows up as missing. "Install missing" (and bare `skillshare install`) then cloned it again at the old path, leaving two copies that both sync to targets, and reconcile could hand the new copy's record to the moved one. A gone record now follows an unrecorded directory of the same name whose files match the recorded hashes, when exactly one such directory exists. Install-from-config skips such entries and reconcile re-keys the record, so the moved copy keeps its source. Same-name skills with other files are left alone, so an update can never overwrite them from that source. Refs: #510 * fix(install): keep audit acceptances and unreadable links out of moves Re-keying a moved skill went through Remove, which also drops the audit findings accepted for the old path, so an unchanged skill could block or prompt again on its next update. MoveEntry now carries them to the new key. A record below a first-level source link that cannot be read looks gone to Lstat, so an identical copy elsewhere could take its record while the link was down. Such records are no longer matched as moved. * fix(install): drop legacy-path acceptances and respect lock pins on move A legacy basename key such as `demo` with group `old` keeps its accepted audit findings under `old/demo`. MoveEntry removed only the key's own acceptances, so the old path kept them and a later skill placed there would inherit them without a new --force. It now deletes the old path. When the lockfile pins another commit than the moved copy holds, treating the copy as the moved skill re-keyed its stale record and let the project lock be rewritten with the older commit. Such copies no longer count as a move, so the pinned commit is installed as before. * fix(install): search for moved skills only where reconcile looks The search for a moved copy walked into installed skills and tracked checkouts, which reconcile skips. A copy found there made install skip the skill, then reconcile never saw the copy and pruned the record, and in project mode the config entry with it. The search now stops at the same boundaries. * fix(install): never take a recorded skill as another's moved copy Two identical skills can be recorded at different paths. When one of them went missing, the other matched its hashes and was taken as its moved copy, so install skipped the missing skill and reconcile pruned its record. A directory with a record of its own is now never a move destination. * fix(install): derive moved-copy paths from the resolved source root sourcewalk.WalkDir reports paths under the resolved source root, but the moved-copy search took them relative to the unresolved one. With a linked source (or Windows short temp paths) every path came out as ../..., so the installed-skill boundary never matched and a copy inside an installed parent could be taken as the move, after which reconcile pruned the record. The search now resolves the root first, as reconcile does. * fix(install): move a record only to one copy of what the config declares Three cases still let a move drop or misplace a record: - In project mode the manifest can point a skill at a new source while a copy of the old one exists elsewhere; that copy was taken as the skill, so the new source was never installed. The record's source and branch must now match the config entry. - A git checkout reconcile treats as tracked could be accepted before the tracked boundary was checked; the boundaries now run first. - With two identical copies, reconcile re-keyed the record to whichever it walked first. Both reconcile and the install-from-config search now require exactly one destination, and reconcile decides after the walk. * fix(install): clear accepted findings left at a move destination A removed legacy grouped entry can leave findings accepted for its path behind. MoveEntry only wrote the destination when the moved skill had its own acceptances, so a skill moved into that path inherited findings it never accepted. The destination is now cleared before the transfer. * fix(install): follow a moved skill only while its declaration still matches The install-from-config search compared source and branch but not the tracking mode, so a skill switched to tracked was satisfied by an old plain copy and never cloned. Project reconciliation, which other installs also run, inferred moves without looking at the manifest at all. A record whose declaration now names another source could follow a copy of the old source, after which the manifest entry was rewritten to that old source. Moves in project mode now require the declaration to still match the record, through the same MatchesDeclaration check the install path uses. * fix(install): infer no move while a source link is unreadable An unreadable followed source link can hide a second identical copy, so a copy that looked unique could take the record arbitrarily. Reconcile and the install-from-config search now infer a move only from a complete inventory; reconcile already keeps the gone record in that case. * fix(install): infer no move when the source walk hit an error Both walks dropped traversal errors, so an unreadable directory that hid a second identical copy left the visible one looking unique and it could take the record. Any walk error now counts as an incomplete inventory, like an unreadable source link, and no move is inferred from it. * fix(install): keep a record whose move waits on a failed walk When a walk error deferred a move, the walk still counted as complete, so pruning dropped the gone record along with its accepted audit findings and it could never follow the copy. A failed walk that deferred a move now marks the inventory incomplete, as an unreadable source link does; a failed walk with no move candidate keeps the old behavior. Also correct InstallFromConfig's comments, which still said reconcile runs only after an install. * fix(install): move a moved skill's gitignore rule in project mode Project reconcile added the managed ignore rule for a moved skill's new path but left the old one, and the gitignore update only ever adds. If the old path later held source-controlled files, Git kept ignoring them without a word. Reconcile now reports the paths records moved away from, and project reconcile removes their managed rules before adding the new. * test(config): skip the unreadable-directory reconcile test on Windows Windows does not stop reading a directory created with mode 0, and os.Geteuid reports -1 there, so the root-only skip let the test run and fail on the Windows runner. * fix(install): count a candidate that cannot be hashed as an incomplete search MovedEntryKey dropped a same-name candidate whose files could not be hashed, so a readable identical copy beside it looked unique and could take the record. It now returns the hash error, and reconcile and the install-from-config search treat it like a walk error: no move is inferred from that scan, and reconcile keeps the record waiting.
skillshare
English · Deutsch · Español · Français · 日本語 · 한국어 · Português · 简体中文 · 繁體中文
Your AI coding setup, everywhere.
Manage skills, agents, rules, MCP connections and hooks in one place.
For Claude Code, Codex, Pi, OpenCode and more.
Website • Install • Quick Start • Highlights • Screenshots • Desktop App • Docs
Note
Latest: v0.25.0 —
skillshare mcp serveserves your skills over MCP (the SEP-2640 Skills extension) to agents that can only reach an MCP endpoint, withlist_skillsandread_skilltools for clients without the extension, and the dashboard's Add server gets a Skillshare tab for it;skillshare linkandunlinkadd or remove a folder kept elsewhere, such as your own checkout or an external drive, as a followed source link, also from the Skills page; and the Oh My Pi (omp) target gains MCP, code hooks, plugins and extension selection. All releases →
Why skillshare
Switching AI tools should not mean rebuilding your setup. skillshare gives your skills and other AI resources a home you control.
- Switch tools, keep your skills — edit once, then sync to Claude Code, Codex, Pi and the other tools you use.
- Take your setup with you — version your source in Git and pull it onto another machine.
- Share with your team — keep project resources with your code and distribute shared skills through tracked repositories.
One teammate uses Claude Code, another uses Codex. Keep their shared code-review checklist in .skillshare/ alongside the project. New teammates install the declared skills and sync to the configured tools instead of copying instructions from chat. Team onboarding →
Use the desktop app or CLI to manage everything locally, audit skills before use, and choose what each tool receives.
Coming from another tool? Migration Guide · Comparison
CLI and UI Preview
| Skill Detail | Security Audit |
|---|---|
![]() |
![]() |
| UI Dashboard | UI Skills |
|---|---|
![]() |
![]() |
Installation
Tip
Use skillshare from your desktop. Get Skillshare App for macOS (Apple Silicon), Windows and Linux. First launch helps you install or locate the CLI, choose your AI tools and run your first sync. Installation guide.
Desktop App — visual setup and daily management
Skillshare App puts skills, agents, MCP and hooks in a desktop window. Install the app, open it, and follow first-launch setup.
macOS (Apple Silicon), with Homebrew:
brew tap runkids/tap
brew install --cask skillshare-app
Windows / Linux, or a manual macOS install: Download the latest app installers. See the Desktop App guide for platform details.
CLI: macOS / Linux
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh
The script installs to ~/.local/bin by default, so normal installs and updates do not need sudo. If the installer prints PATH setup instructions, follow them before running skillshare. Add the suggested line to your shell config (such as ~/.zshrc or ~/.bashrc) for future terminals. Set INSTALL_DIR to use another location.
Windows PowerShell
irm https://raw.githubusercontent.com/runkids/skillshare/main/install.ps1 | iex
CLI: Homebrew
brew install skillshare
Tip: Run
skillshare upgradeto update to the latest version. It auto-detects your install method and handles the rest.
GitHub Actions
- uses: runkids/setup-skillshare@v1
with:
source: ./skills
- run: skillshare sync
See setup-skillshare for all options (audit, project mode, version pinning).
Shorthand (Optional)
Add an alias to your shell config (~/.zshrc or ~/.bashrc):
alias ss='skillshare'
Quick Start
skillshare init # Create config, source, and detected targets
skillshare sync # Sync skills to all targets
How It Works
- macOS / Linux:
~/.config/skillshare/ - Windows:
%AppData%\skillshare\
┌─────────────────────────────────────────────────────────────┐
│ Source Directory │
│ ~/.config/skillshare/skills/ ← skills (SKILL.md) │
│ ~/.config/skillshare/agents/ ← agents │
│ ~/.config/skillshare/extras/ ← rules, commands, etc. │
└─────────────────────────────────────────────────────────────┘
│ sync
┌───────────────┼───────────────┐
▼ ▼ ▼
┌───────────┐ ┌───────────┐ ┌───────────┐
│ Claude │ │ OpenCode │ │ OpenClaw │ ...
└───────────┘ └───────────┘ └───────────┘
| Platform | Skills Source | Agents Source | Extras Source | Link Type |
|---|---|---|---|---|
| macOS/Linux | ~/.config/skillshare/skills/ |
~/.config/skillshare/agents/ |
~/.config/skillshare/extras/ |
Symlinks |
| Windows | %AppData%\skillshare\skills\ |
%AppData%\skillshare\agents\ |
%AppData%\skillshare\extras\ |
NTFS Junctions for folders (no admin required); file symlinks need Developer Mode, otherwise copied |
| Imperative (install-per-command) | Declarative (skillshare) | |
|---|---|---|
| Source of truth | Skills copied independently | Single source → symlinks (or copies) |
| New machine setup | Re-run every install manually | git clone config + sync |
| Security audit | None | Built-in audit + auto-scan on install/update |
| Web dashboard | None | skillshare ui |
| Runtime dependency | Node.js + npm | None (single Go binary) |
Highlights
Install & update skills —from GitHub, GitLab, or any Git host
skillshare install github.com/reponame/skills
skillshare update --all
skillshare target claude --mode copy # if symlinks don't work
Symlink issues? — switch to copy mode per target
skillshare target <name> --mode copy
skillshare sync
Security audit —scan before skills reach your agent
skillshare audit
Project skills —per-repo, committed with your code
skillshare init -p && skillshare sync
Agents —sync custom agents to agent-capable targets
skillshare sync agents # sync agents only
skillshare sync --all # sync skills + agents + extras + MCP + hooks together
Extras —manage rules, commands, prompts & more
skillshare extras init rules # create a "rules" extra
skillshare sync --all # sync skills + agents + extras + MCP + hooks together
skillshare extras collect rules # collect local files back to source
MCP connections —configure once for Claude Code, Codex, Pi, VS Code, OpenCode and more
skillshare mcp add # guided URL or JSON setup
skillshare sync mcp --dry-run # preview native configuration changes
skillshare sync mcp # apply connection settings
Keep definitions in config.yaml or reference a separate mcp.yaml.
See MCP setup
for examples, environment references and importing existing connections.
Manage native hooks without executing them:
skillshare hooks add check --file ./check.yaml
skillshare hooks sync --dry-run
skillshare hooks sync
Plugins —install a complete plugin and pick which tools receive it
skillshare plugin add # guided: source, plugin, targets, review
skillshare plugin add owner/repo --target claude --target codex --no-tui
skillshare sync plugins --dry-run # plugins sync separately from sync --all
Existing native installations can be adopted with plugin import.
See Manage plugins across tools.
Shell completion —tab-complete commands, flags, and subcommands
skillshare completion bash --install # also: zsh, fish, powershell, nushell
Local checkpoints — commit source changes without pushing
skillshare commit -m "Update review skill"
skillshare commit --dry-run
Web dashboard — visual control panel
skillshare ui
Contributing
Contributions welcome! Open an issue first, then submit a draft PR with tests. See CONTRIBUTING.md for setup details.
git clone https://github.com/runkids/skillshare.git && cd skillshare
make check # format + lint + test
Tip
Not sure where to start? Browse open issues or try the Playground for a zero-setup dev environment.
Contributors
Thanks to everyone who helped shape skillshare.
Support skillshare ❤️
skillshare is free and open source.
If skillshare saves you time, consider buying me a coffee. Every contribution helps with ongoing development, cross-platform testing, documentation, and maintenance.
You can also help by giving skillshare a ⭐ on GitHub!
Star History
License
MIT































































































