* feat(ui): check plugin updates on load and update them in one batch Updating plugins took four steps each: press Check updates, press Update on one row, review a second preview, apply, then check again because the list did not know the update had happened. Six plugins meant six rounds. The page now checks once in the background when it opens, so rows show their new version without a click. The header's Check updates button becomes "Update N" when something is behind and opens one dialog: every plugin with an update is ticked, a plugin on several Agents is one row whose Agents can be left out, and imported installs Skillshare cannot update sit apart. One button runs them in turn through the existing preview and apply, so no new API is needed. Progress, results, errors and per-Agent retry stay in the same dialog, and the applied results update the page state, so nothing has to be checked again. The count and the dialog both come from what is still behind after the last check, limited to Agents that can be updated from here, so a partial batch is not offered again and Agents with check but no update (OMP, Antigravity CLI, Grok) do not inflate the count. * fix(ui): keep batch plugin updates to what the user reviewed Codex review of #527 found four ways the batch update could act on something other than what the dialog showed: - A source that moved between the background check and the click was installed straight from the fresh preview, so a newer version or new components went in unreviewed. The batch now compares each fresh plan with the version and commit the check showed, applies nothing when they differ, says so on the row, and runs a quiet check so the next dialog shows the new version for review. - A retry of the failed Agents that failed again lost that subset, so a third try re-sent Agents that had already updated. A failed row now always keeps the Agents it failed on. - An update the server skipped (its marketplace gone, say) counted as done: the row said updated and the plugin left the update count. Skipped outcomes now keep the Agent pending and show as skipped. - A plugin removed after the check stayed in the update count and failed with "not found" when picked. Pending updates now drop any plugin or Agent binding the inventory no longer has. * fix(ui): show a manual check's result and each Agent's own version move Codex's second review of #527 found two gaps: - A check the user pressed that found nothing to update from here (only imported installs, or everything current) opened nothing, so the "update inside the Agent" guidance and the up-to-date result never showed. The check now reports whether it came back, and a check the user asked for opens the dialog; the background check on load stays quiet. - A plugin on several Agents showed one version move built from the first Agent's installed version and the first new version found, which can mix Agents that come from different sources. The row now shows one move only when every Agent makes the same one, and each Agent's own move otherwise. * fix(plugin): carry the source digest on a check so a batch update can tell it moved Codex's third review of #527: a local-directory plugin has no commit, so when its files changed again after the check while the manifest version stayed the same, the batch's version and commit comparison passed and the fresh preview was applied without the user seeing it. The check copied the installed binding, so its digest was the one already installed, not the source's. It now sets the discovered digest alongside the version and commit, as the update preview already does. The dashboard keeps that digest with each update it found and refuses to apply when the fresh preview's digest differs, marking the row as changed since the check. An npm package has no digest and is unaffected. * fix(ui): list blocked check results and drop unticked Agents from the batch Codex's fourth review of #527: - A check can mark an Agent blocked when the updated source no longer offers a compatible plugin for it. The update dialog listed only updatable, native-check and up-to-date results, so it hid the block and could say everything was current. Blocked results now get their own section with the reason, and the empty state says nothing can be updated from here rather than that everything is up to date. - An Agent unticked after the check stayed in the pending updates; picking it produced a no-op that the batch reported as updated. Pending updates now skip bindings with sync off, as the row's own behind count already does. * fix(ui): count partly skipped plugins as updated and surface a failed re-check Codex's fifth review of #527: - When one Agent of a plugin updated and another came back skipped, the row was marked skipped, the summary counted no update, and the Agent that did update was not shown. A row now names which Agents updated and which were skipped, and the summary counts any plugin with an updated Agent. - After a source moved since the check, the follow-up check ran quietly, so if it failed the stale update stayed offered and every retry hit the same skip. The moved plugin now leaves the found updates, and the follow-up check reports its failure like any check the user started.
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
































































































