> ## 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.

# Quickstart

> Set up MasterSkills on a machine in three commands, then let your agent take over.

## For developers

<Steps>
  <Step title="Install the CLI">
    ```bash theme={"dark"}
    npm install -g @masterskills/cli
    ```

    Requires Node ≥ 20. The CLI checks for new versions once a day and prints a notice when one
    is available — update with the same command.
  </Step>

  <Step title="Register MasterSkills with your agents">
    ```bash theme={"dark"}
    masterskills install
    ```

    The CLI detects every supported coding agent on your machine (Claude Code, Codex, Cursor,
    Gemini CLI, and [70+ more](/guides/supported-agents)) and installs the MasterSkills skill into
    each of them. That skill is how your agent learns to search, install, update, and publish
    skills on your behalf.

    Restart your agents once so they load it.
  </Step>

  <Step title="Authorize this device">
    ```bash theme={"dark"}
    masterskills login
    ```

    Your browser opens once. Confirm the code shown in the terminal, pick your organization, and
    the device receives a lifetime token — you will not log in again on this machine. See
    [Devices & authentication](/concepts/devices).
  </Step>

  <Step title="Talk to your agent">
    Setup is done. From here on, use plain language in your agent:

    > "Which skills do we have for the booking flow?"
    > "Install `@acme/api-conventions`."
    > "Publish the skill in ./skills/review-checklist to the team."
    > "Any skill updates?"

    The agent always asks before writing to disk and before publishing —
    [two rules it can never break](/concepts/trust).
  </Step>
</Steps>

<Note>
  Newly installed skills load in **new** agent sessions. If a skill doesn't seem active, restart
  the agent session first.
</Note>

## For admins

Setting up an organization takes about two minutes:

<Steps>
  <Step title="Create the organization">
    Sign in at [masterskills.dev](https://masterskills.dev) with GitHub or Google — there are no
    passwords. Create your organization when prompted.
  </Step>

  <Step title="Share one invite link">
    Copy the invite link from the members page. Optionally restrict it to your email domain
    (for example `@acme.com`) so matching teammates join instantly; everyone else lands in a
    pending queue you approve. See [Onboard your team](/guides/onboard-your-team).
  </Step>

  <Step title="Everyone runs the setup once">
    Each teammate installs the CLI (`npm install -g @masterskills/cli`) and runs
    `masterskills install` and `masterskills login` once on their machine. Every active member
    sees every skill and kit in the organization.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Publish your first skill" href="/guides/publish-a-skill">
    Turn a local skill folder into a versioned `@org/slug` package.
  </Card>

  <Card title="Build a kit" href="/guides/build-a-kit">
    Bundle skills so the whole team installs them with one command.
  </Card>
</CardGroup>