Skip to main content
No. The only thing that ever leaves your machine is the skill folder you explicitly approve for publishing — and you see its full file manifest first. Files that look like secrets are excluded from the package and reported to you. Searching, installing, and updating send metadata (skill names and versions), not your code.
Skill installs cover 70+ coding agents — the full skills.sh agent set, auto-detected per machine. Driving MasterSkills conversationally works in any agent that loads skills and can run shell commands; Claude Code is the reference experience. See Supported agents.
The client is: the masterskills CLI is MIT-licensed at masterskills-dev/masterskills. The registry at masterskills.dev is a hosted service.
Self-hosting the registry is part of the Enterprise plan. The CLI targets a self-hosted server with masterskills login --api-url <host> or the MASTERSKILLS_API_URL environment variable. Talk to us for Enterprise.
Three users, one device per user — and deliberately no limits on skills, versions, or installs on any plan. Free is the trial: run the full product with a small group, upgrade when you roll it out to the team. Current pricing: masterskills.dev/pricing.
Skills load when an agent session starts. Restart the agent (or open a new session) after installing. If it’s still missing, masterskills agents shows whether the agent was detected and where its skills directory is, and masterskills link repairs links.
A required skill shows up in every member’s update check until installed — and that is all. It is never installed silently; the user always confirms. Silent writes would break the product’s first trust rule.
skills.sh installs public skills; MasterSkills distributes and manages private ones — permissions, versions, devices, and an audit trail. A git repo is a skill source, and repo-local skills stay untouched; the registry adds the permission, versioning, and distribution layer a repo doesn’t have.
Deliberate. Publishing goes through one pipeline — manifest shown, secrets scanned, approval required — whether a human or an agent triggers it. A web upload form would be a second path around those guarantees.
GitHub or Google OAuth only. No passwords exist in the product.
Something not covered here? Open an issue at masterskills-dev/masterskills.