Skip to main content

​
Through your agent

The normal way. Ask in plain language:
You: which skills do we have for bookmaker? Agent: Not on this machine. Your org has 3: @acme/bookmaker-content-rules v4 · @acme/bookmaker-api-integration v2 · @acme/bookmaker-qa-checklist v1 Which ones should I install? You: the first two Agent: Both installed for every detected agent. They’ll be active in new sessions.
The agent searches your organizations’ catalog, shows what exists and what’s already installed, and installs only after you confirm — rule 1.
Installed skills load in new agent sessions. Restart the agent (or open a new session) after installing.

​
From the CLI

The same operations by hand:
list and search take --json for machine-readable output — each entry includes installedVersion and updateAvailable alongside the registry data.

​
What install actually does

  1. Downloads the skill package and verifies its content hash against the registry record — a mismatch aborts before anything touches disk.
  2. Writes the skill to the central store: ~/.masterskills/skills/<org>/<slug>.
  3. Links it into every detected agent’s skills directory (flattened to org--slug). One install covers Claude Code, Codex, Cursor, and every other detected agent at once.

​
Removing

“Remove the QA checklist skill from this machine.”
or:
Removal is local — files and links on this machine only. The skill stays published for the rest of the organization. Retiring a skill org-wide is unpublish, a human-only action.