> ## Documentation Index
> Fetch the complete documentation index at: https://docs.masterskills.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# masterskills add

> Install skills — or whole kits — from the registry into every detected agent.

```bash theme={"dark"}
masterskills add <names...>

masterskills add @acme/api-conventions
masterskills add @acme/api-conventions @acme/review-checklist
masterskills add @acme/ai-team          # kits install with the same command
```

Names are full `@org/slug`. Skills and [kits](/concepts/kits) share one namespace, so `add` resolves the name automatically — a kit installs every skill inside it that you're entitled to see.

## What happens

1. The package is downloaded and its **sha256 verified** against the registry's recorded content hash — a mismatch aborts before anything is written.
2. The skill lands in the central store (`~/.masterskills/skills/<org>/<slug>`).
3. Links are created in every detected agent's skills directory (`org--slug`). One `add` covers all agents on the machine.

<Note>
  New skills load in **new** agent sessions — restart the agent after installing.
</Note>

<Warning>
  For agents: `add` is approval-gated. Confirm the exact skill list with the user before running
  it — [rule 1](/concepts/trust).
</Warning>

Private skills require membership in the owning organization; public skills install by full name from any signed-in device.