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

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the atlanai CLI; `atlanai --map json` prints its command map. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.

# Bring your skills into Agent Registry

> Sign in to the desktop app, import the skills and sessions on your computer, and move one skill to a team workspace.

Agent Registry starts from what is already on your computer. The desktop app
reads the skills and sessions that Claude Code and Codex keep on your computer
and brings them into your personal workspace. Without that import, your
registry is empty, and your teammates cannot find the skills you already rely
on.

In this lesson, you sign in, answer two setup questions, and let the app
import your setup. Then you open one of your skills and move it to a team
workspace. The import gives you a personal workspace that holds your own
skills. The move makes one skill visible to your team.

<Tip>
  **At the end of this lesson:** your **Personal** workspace lists the skills
  and sessions the app found on your computer. One of those skills now belongs
  to a team workspace, where its members can find and use it.
</Tip>

## Before you begin

Before you start, make sure you have:

* **Desktop app**: installed on macOS or Windows. See
  [Install desktop app](/administer/desktop/how-tos/install).
* **Organization account**: your organization sign-in. Ask your admin to invite
  you if you do not have one.
* **Claude Code or Codex** (optional): with at least one skill installed. If
  neither is installed, the import finds nothing to bring in, and you can
  stop after the import step.
* **Team workspace** (optional): one you can add skills to, for the last two
  steps. Your admin or a workspace admin can create or share one.

## Bring your setup into Agent Registry

First-run setup has four parts: sign in, answer setup questions, join team
workspaces, and import. Then you open a skill and move it.

<Steps>
  <Step title="Sign in">
    Open the desktop app. On **Welcome to Agent Registry**, select **Get started**.

    The app opens your browser to sign in. Approve access there, then return to
    the app. While you sign in, the app shows **Continue in your browser**. If
    the browser does not open, select **Reopen browser window**.

    Sign-in matters because your identity decides which organization and
    workspaces you see. Everything you import is tied to it.
  </Step>

  <Step title="Answer setup questions">
    The app asks two questions:

    * **What brings you here?**: choose the option closest to what you plan to
      do, then select **Continue**.
    * **Tell us about yourself**: confirm your name and what you do, then
      select **Continue**. You can select **Skip for now** instead.

    Your answers tailor the app. They do not change your access.
  </Step>

  <Step title="Join team workspaces">
    The next screen shows the organization you are in and the team workspaces
    you can join. Select **Join** beside each workspace your team uses, then
    select **Continue**.

    Team workspaces are where a team shares skills. Joining one adds you as a
    **Builder**, so you can find its skills and add your own. If your
    organization has no team workspaces yet, the screen says so, and you can
    continue.
  </Step>

  <Step title="Import your setup">
    On first run, the app may show **Setting up the Registry CLI…** while it
    finishes installing the components it needs.

    The app then shows **Reading your setup** and brings in your skills,
    plugins, and sessions. It reads only fixed folders in your home folder:
    `~/.claude`, `~/.codex`, and `~/.agents`. When it finishes, it shows
    **Your personal workspace is ready.** and a summary under **Your setup**.

    Select **Continue**. The app opens your **Personal** workspace.

    Only you can see your personal workspace. If you see **Nothing to bring in
    yet.**, Claude Code and Codex have no skills or sessions on this computer. Your workspace still exists, and later
    skills and sessions land in it automatically.
  </Step>

  <Step title="Open one of your skills">
    In **Personal**, find your skills under Browse. When the workspace holds
    more than one kind of item, select the **Skill** tab first. Select a skill.

    The skill page has the tabs **Overview**, **Source**, **Releases**,
    **Relationships**, **Usage**, and **Security**. Open **Source** to see the
    files the app imported and where the skill came from. Compare them with the
    skill folder on your computer to confirm the import is complete.
  </Step>

  <Step title="Move skill to team workspace">
    On the skill page, select **Share**. Because the skill is in your personal
    workspace, the panel says **It is in your personal workspace.** and offers
    **Move it to a team workspace**. Select **Move**.

    In the **Move** dialog for your skill, find the destination workspace.
    Each workspace shows **You can add skills** or **Only admins can add skills**. Choose one
    you can add to, check that the dialog says its members will get access,
    then select **Move**.

    The skill is now managed from that workspace. Its members can find and use
    it. To undo, open **Share** again and move the skill back to **Personal**.
  </Step>

  <Step title="Verify skill visibility">
    Open the team workspace and find the skill under Browse, in the **Skill**
    tab when one is shown. It appears in the list.

    Your own view proves the skill is in the workspace, not that every member
    can see it. When it matters, ask a teammate who is a member of that
    workspace to search for it. If the skill is missing for you or a teammate,
    see [Workspace access errors](/administer/workspaces/troubleshooting/workspace-access-errors).
  </Step>
</Steps>

## What you have accomplished

Your **Personal** workspace holds the skills and sessions the app found on your
computer, and keeps receiving new ones. One skill now lives in a team workspace,
where its members can find it, use it, and see its usage.

If sign-in or the import cannot connect, see
[Network requirements](/administer/desktop/references/network-requirements):
the hosts the desktop app must reach.

## What's next

[Discover and use skills](/registry/skills/how-tos/discover-and-use): find skills your team shares and open them in Claude Code or Codex.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.