* feat(mcp): warn when a local server runs an unpinned package or image An entry such as `npx -y some-mcp` fetches whatever the registry serves at every Agent start, so a compromised release reaches the machine on the next launch without anyone noticing. The MCP local-server security guide (spec 2026-07-28) names version pinning as a baseline and points out that a container tag can move while a digest cannot. `mcp check` now adds a `pin` finding from command and args alone, with no network: npx, uvx and `pipx run` with no version or `latest`, and `docker`/`podman run` with no tag or `latest`, are warnings; an image pinned by tag but not by `@sha256:` digest is info. Value-taking run flags are skipped so hardened lines such as `--cap-drop ALL` are not read as the image. Warnings keep the exit code at 0, as before. * fix(mcp): check every npx package, word pin warnings in the dashboard, document them in doctor Codex review on #559: - npx accepts --package more than once and fetches each one, but the pin check stopped at the first, so `npx --package=lodash@4.17.21 --package=cowsay cowsay` passed although cowsay is unpinned. Every --package/-p value is now checked. - The dashboard words env, command and dns findings in the viewer's language but showed the new pin warning in English. It now has its own sentence for an unversioned package and for an untagged image in every locale. The dashboard hides info findings, so the digest note needs none. - doctor promotes check warnings, so an unpinned launcher now shows there; its docs list the pin check. The mcp check runbook gains a step for the pin check. * fix(mcp): check uvx --with packages and ignore environment markers in pins Codex review on #559: - uvx --with (-w) installs each named package beside the tool, so an unpinned one moves just like an unpinned tool, but the pin check skipped it as a flag value. Every --with requirement is now checked next to the --from or command package. - In `--from 'mcp-server; python_version == "3.12"'` the == belongs to the environment marker, not to the package, yet it read as a pinned version. Only the requirement before ';' is inspected now. * fix(mcp): treat only exact versions as pins, and pin the docs' own examples Codex review on #559: - npm resolves a dist-tag (`@next`) or a range (`@^1.2.3`) to whatever release matches at launch, yet any selector but `latest` passed as pinned. An npx package is pinned now only by an exact semver version, the rule Pi bindings already use. - `==1.*` is a prefix match in Python version specifiers, so `uvx --from 'mcp-server==1.*'` can pick up a new 1.x release; it is no longer read as a pin. - The Context7, Playwright and filesystem examples in the docs and the built-in skill launched unpinned packages, so copying them produced the new warning at once. They now name the current registry version.
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.10 — The MCP page opens each Agent's MCP config file, or the folder that holds it, straight from the dashboard, so you can edit
opencode.jsonor.cursor/mcp.jsonin any program without setting$EDITOR. Each project's MCP tab now lists that project's Agent files with the same Open folder, Open in editor and Copy path buttons. 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

































































































