> ## 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 SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. 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. > These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces. # Use skills in coding agents > Hand a reviewed skill to Claude Code or Claude Desktop from its profile, or find it from Codex through MCP, so you can use it in your current task. Using a skill in a coding agent puts one reviewed skill to work in your current task: Claude Code and Claude Desktop take it from the skill's profile as a prefilled prompt, and Codex, which has no **Open in** handoff, finds it through the Atlan MCP connection. Use it when you have reviewed a skill and want an agent to apply it now. To give every session Atlan's tools rather than one skill at a time, [connect your coding client](/clients/index) to the Atlan MCP endpoint instead; the two flows are separate. ## Before you begin Before you start, make sure you have: * **Reviewed skill**: You have confirmed the skill's workspace, source, and live version in Atlan. See [Find and assess skills](/registry/skills/how-tos/discover-and-use). * **Claude Code or Claude Desktop**: Installed, in a version that accepts the handoff link. * **Codex**: Connected to Atlan. See [Connect Codex](/clients/openai/how-tos/codex). * **Workspace access**: Your identity can open the workspace where the skill lives. **1. Open skill profile** In Atlan, open the profile of the skill you reviewed. You hand the skill over from here in Claude, and compare against it in Codex. **2. Hand skill to agent** **Claude Code** Select **Open in**, then choose **Claude Code**. Claude Code opens with a prompt for the selected skill. If Claude Code does not open, return to **Open in**, select **Copy agent prompt**, and paste the prompt into Claude Code yourself. See [Claude does not open from Open in](/registry/skills/troubleshooting#claude-does-not-open-from-open-in). **Claude Desktop** Select **Open in**, then choose **Claude Desktop**. Claude Desktop opens a conversation with a prompt for the selected skill. If Claude Desktop does not open, return to **Open in**, select **Copy agent prompt**, and paste the prompt into Claude Desktop yourself. See [Claude does not open from Open in](/registry/skills/troubleshooting#claude-does-not-open-from-open-in). **Codex** Start Codex in the repository where you are working, and ask it to find or inspect the skill by name. Codex can use only the Atlan tools available to your identity and workspace. A connected server does not guarantee that every skill or registry tool is available. **3. Verify skill before use** **Claude Code** Read the prefilled prompt and confirm it names the skill you reviewed, then submit it. The handoff only fills in the prompt: it does not send it, and it does not prove that the client installed or ran the skill. **Claude Desktop** Read the prefilled prompt and confirm it names the skill you reviewed, then submit it. The handoff only fills in the prompt: it does not send it, and it does not prove that the client installed or ran the skill. **Codex** Compare what Codex returned with the skill's purpose, source, and released version in Atlan. Use the skill only after you confirm it fits the current task and its **Security** tab shows a passing scan. An MCP connection does not install a skill package. ## Troubleshooting If Claude does not open or the prompt does not appear, see [Skill errors](/registry/skills/troubleshooting). If `atlan` is not listed in Codex or tools are missing, see [Connect client to MCP Gateway](/gateway/mcp/how-tos/connect-a-client#troubleshooting). ## Next steps * [Connect coding clients](/clients/index): Give every session governed Atlan tools instead of one skill at a time. ## See also * [Find and assess skills](/registry/skills/how-tos/discover-and-use): Choose and review a skill before you use it. * [Connect Claude Code](/clients/claude/how-tos/claude-code): Set up the Atlan MCP connection in Claude Code. * [Connect Codex](/clients/openai/how-tos/codex): MCP setup and connection checks for Codex. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.