skillshare

Why it's ranked here

The problem is real and gets worse with every agent you add, and skillshare treats it as declarative state rather than a pile of install commands. It ships as one Go binary with no runtime dependency, no registry and no telemetry, under an MIT license. Coverage goes past skills: agents, rules, plugins and MCP connections all route through the same source. The dashboard and the command line call the same domain code, so the two surfaces do not drift, and the repository carries a separate integration test suite and scripted end-to-end runbooks.

What's good

Dry-run exists where it matters: MCP and plugin syncs can be previewed before they touch any tool's config. Machine-readable output is treated as a contract, so JSON modes print only structured data and skip the update check. Per-target include and exclude filters decide which skills reach which tool. Hub indexes can live on private Git hosts over SSH, and the index reader refuses paths that escape the cloned repository. The local dashboard server sets read, write and idle timeouts and shuts down cleanly on interrupt.

Tradeoffs

The one-line installer pipes a tarball into tar and moves it into a system binary folder, asking for sudo if needed, without checking it against the published checksums file. Plugins sync separately and are left out of the sync-everything command, which is easy to miss. Hub search is a plain substring match sorted by name, with no relevance ranking. The dashboard reloads configuration from disk on nearly every API request, which is simple but means a broken config surfaces as a server error. Symlinks can misbehave on some setups, which is why copy mode exists.

How to use it well

Best for someone running two or more coding agents who wants one versioned folder of skills and rules. Run init, let it detect installed tools, then sync. Keep project skills in the repository so teammates get them on clone, and track a shared team repository for organization-wide ones. Run the audit before syncing anything installed from a third party. Use Homebrew, or fetch the binary yourself and compare checksums, rather than the curl pipe. It manages files; it does not write skills for you or judge whether they are any good.

Observed

License

MIT

Language

Go, with a React and Vite web dashboard

Packaging

Single static binary built with cgo disabled; shell and PowerShell installers, Homebrew tap, GitHub Action

Platforms

Linux, macOS and Windows on amd64 and arm64

Interfaces

CLI, terminal UI, local web dashboard backed by an HTTP API

Configuration

Published JSON Schema for the global config file

Install script

install.sh does not verify archive checksums

Tests

Separate CLI integration test directory and end-to-end runbooks described in the repository docs