Skillshare Sync Manager
Manage AI coding resources in one place and sync them across tools and machines.
- Source repo
- runkids/skillshare
- Stars
- ★ 2.8k
- Last updated
- 1d ago
- License
- MIT
- Primary language
- Go
- FA score
- 60/100 · Some gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Cost
- Free, no paid service needed
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- A developer who switches between Claude Code and Codex and wants one maintained skill source.
- Not a fit if
- Teams that want a vendor-hosted service to manage configuration and sync
- Source review
- 60/100 · Some gaps
What does this agent do, and when should you use it?
Skillshare is a Go CLI for managing AI coding setup, with a desktop app and a local web dashboard. It keeps skills, agents, extras such as rules and commands, MCP connections, hooks, and plugins in a central source directory, then syncs them to targets including Claude Code, Codex, Pi, and OpenCode. On macOS and Linux it uses symlinks by default; on Windows it uses directory junctions, while file symlinks require Developer Mode and otherwise files are copied. You can keep the source in Git for another machine or track project resources alongside a repository for team sharing. It runs locally and includes skill auditing plus automatic scans on install or update; the README does not describe the audit rules in full.
Run skillshare init to create configuration, source directories, and detected targets; use skillshare install to fetch skills from GitHub, GitLab, or another Git host, then skillshare sync to distribute selected resources. skillshare audit checks skills, while skillshare sync mcp applies MCP connection settings. Hooks can be managed with skillshare hooks add and skillshare hooks sync; agents and plugins can also be synced separately. The output is links or copies in target-native locations, along with changes to tool configuration such as MCP settings. skillshare ui opens a local web control panel, and the desktop app provides visual setup and daily management.
- A developer who switches between Claude Code and Codex and wants one maintained skill source.
- A developer who wants to version configuration in Git and restore the setup on a new machine.
- A team that wants shared resources, such as a code review checklist, tracked with its project repository.
- An engineering team that needs to configure MCP connections or hooks across multiple AI tools.
- A user who wants to run a local audit before installing third-party skills.
How do you install or deploy this agent?
The CLI supports macOS, Linux, and Windows. The macOS/Linux installer defaults to ~/.local/bin; follow its PATH instructions if shown. Homebrew is also supported. The desktop app has installers for macOS (Apple Silicon), Windows, and Linux; first launch helps install or locate the CLI. The README does not list additional runtime or API credential requirements.
curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | shirm https://raw.githubusercontent.com/runkids/skillshare/main/install.ps1 | iexbrew install skillshareFor the desktop app on macOS Apple Silicon:
brew tap runkids/tap
brew install --cask skillshare-appHow do you use this agent?
Initialize the configuration and sync to detected targets:
skillshare init
skillshare syncAudit skills and open the local dashboard:
skillshare audit
skillshare uiInitialize project-level resources from a repository:
skillshare init -p
skillshare syncPreview MCP configuration changes before applying them:
skillshare sync mcp --dry-run
skillshare sync mcpWhat are this agent's strengths and limitations?
- One source can manage and sync skills, agents, extras, MCP, hooks, and plugins across tools.
- Supports macOS, Linux, and Windows, with Windows directory junctions that do not require administrator rights.
- Includes
auditand automatically scans skills during install or update. - Git-versioned sources support cross-machine setup and project-level team sharing.
- Offers a desktop app and local web dashboard in addition to the CLI.
- The CLI must be installed and run locally; the README does not describe a hosted sync service.
- On Windows, file symlinks require Developer Mode; without it, files are copied and may not behave like linked files.
- Resource layouts and capabilities vary by target; the README describes syncing to compatible or agent-capable targets.
- The README does not specify the full scope of the skill audit, so it cannot establish that every risk will be detected.
How does this agent compare with similar options?
The README contrasts Skillshare with installing skills separately in each tool: manual installs require repeated copying and provide no built-in audit or web dashboard. Skillshare offers a central source, sync, auditing, and a dashboard. It also mentions migration from other tools without naming specific competitors here.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Skillshare Sync Manager This agent | 60 · Some gaps | CLIFree | ★ 2.8k | 1d ago | Go | Codex · Claude Code |
| Locally Uncensored | 64 · Some gaps | Desktop appFreemium | ★ 2.5k | today | TypeScript | OpenAI API · Claude API |
| Devo Desktop Coding Agent | 58 · Major gaps | Desktop appFree + model costs | ★ 341 | 1d ago | Rust | OpenAI API · Claude API |
| Synara | 52 · Major gaps | Desktop appFree + model costs | ★ 2.1k | 2d ago | TypeScript | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
The README places resources in a local source directory and provides audit plus MCP/plugin dry-run commands. The installer defaults to a user directory and notes Windows permission differences, supporting some data-flow visibility and limited privilege. Sync can change target-tool configuration, but the supplied material does not explain authorization for each operation, protection of sensitive configuration, or rollback, so those criteria receive partial scores. go.mod lists pinned dependency versions, but the evidence includes no vulnerability review. The README and license identify the project and copyright holder; maintenance identity and update responsibility remain unclear.
The README is broadly consistent about the source directory, cross-tool synchronization, and platform-specific link behavior. go.mod pins direct and indirect dependency versions, improving traceability, but the material provides no evidence about dependency availability or failure handling. Failure-message design is not shown, so that score is thin.
The documentation explicitly covers individual migration, team sharing, desktop and CLI use, and targets such as Claude Code, Codex, Pi, and OpenCode, with different installation and linking behavior for macOS, Linux, and Windows. Audit, dry-run, and per-target mode selection show some boundary control; however, scope, target capability differences, and triggering conditions are mostly implied by examples rather than fully defined.
The README has a clear structure with quick start, installation, operating model, feature examples, and documentation links; the license text is complete. Examples are extensive and multilingual, but known limitations are sparse, naming and version information rely mainly on the current-version notice, and the supplied material lacks a full changelog despite release-verification steps. A contribution guide is referenced, but maintenance responsibility and support commitments are not established.
A single resource source, synchronization across AI tools, team sharing, and auditing address a clear problem of duplicated configuration. The command examples are understandable, and dry-run, per-target configuration, and a desktop UI support routine use; however, the material does not fully describe sync-result reporting or the boundaries of its cost and benefit.
The README supports its main workflow and installation claims with concrete commands, paths, a platform table, and the dependency manifest. Independent corroboration across sources is limited: the supplied files include a README, license, dependency manifest, and workflows, but not product implementation or concrete test results. The documentation distinguishes feature descriptions from command examples, while some promotional claims lack checkable detail.
- Sync affects local configuration for target tools; use the documented dry-run and verify targets and contents before applying it in a live environment.
- The supplied material does not show sensitive-configuration handling, recovery from sync failures, or complete test evidence; do not treat those behaviors as verified.
FAQ
Does using Skillshare require a paid service or API key?
Are my configuration and resources uploaded to Skillshare's cloud?
Does syncing on Windows require administrator rights?
Can I sync only one type of resource?
sync --all for multiple resource types.