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

# Publish skills from coding agent

> Let Claude Code or Codex inventory local skills and run the aireg dry run, then publish an approved batch and verify it through MCP.

Publishing from a coding agent lets Claude Code or Codex inventory the skill folders in your repository and preview each publish before anything is sent, while you approve the exact batch. Use it when the skills already live in the repository and you want an agent to check them first. To publish without an agent, run [`aireg publish`](/registry/skills/how-tos/publish-with-cli) yourself.

## Before you begin

Before you start, make sure you have:

* **aireg with the Atlan adapter**: Installed and signed in, with your Atlan registry declared under a name. See [Use aireg with Atlan](/tools/brain/how-tos/use-with-atlan). The examples call that registry `atlan`; use the name you chose.
* **Skill folders**: Folders in the repository, each with `SKILL.md` at its root.
* **Claude Code connected to Atlan (optional)**: Needed only to verify through MCP. See [Connect Claude Code](/clients/claude/how-tos/claude-code).
* **Codex connected to Atlan (optional)**: Needed only to verify through MCP. See [Connect Codex](/clients/openai/how-tos/codex). Project-level MCP configuration loads only after Codex trusts the project.

Publishing through MCP alone takes several steps for each bundle: reserve an upload with `registry__request_file_upload`, upload the ZIP, create its File artifact, then call [`extension__skill__create`](/tools/mcp/skill/references/skill-create). `aireg` does the bundling and upload in one command, so this guide publishes with `aireg` and uses MCP only to verify. Do not ask the agent to upload secrets, customer data, or files outside the skill folders.

**1. Inventory skills and preview publish**

Ask the agent to find the skills and run the dry run without publishing:

```text theme={null}
Inspect ./skills for folders containing SKILL.md. For each skill I name, run
`aireg publish <folder> --to atlan/<workspace-name> --dry-run`. Report the
source folder, whether aireg would add, update, or skip (same) it, and any
error. Do not publish anything.
```

Review the plan, the target workspace, and any naming conflicts.

**2. Approve batch**

Only after the dry run is correct, approve the exact folders:

```text theme={null}
I approve publishing ./skills/release-notes and ./skills/incident-brief to
workspace <workspace-name> with `aireg publish --to atlan/<workspace-name>`.
Publish only those two folders. Do not use `--force`, retry failures, or make any other changes.
```

For what each `aireg publish` option does, see [Publish skills with aireg](/registry/skills/how-tos/publish-with-cli).

**3. Verify published skills**

* **Check in Atlan**: Open each published skill and confirm its version and source files. Atlan serves a new version only after its security scan and any review pass.
* **Check through MCP**: Ask the agent to search for each skill and read it by the handle the search returns.

Publishing a skill does not install it into the agent. In Claude Code, hand a reviewed skill over from its profile with **Open in**. Codex reaches skills through the MCP connection.

## Troubleshooting

If `aireg` reports a sign-in failure or a held or blocked publish, see [Atlan errors in aireg](/tools/brain/troubleshooting/atlan-errors#publish-held-or-blocked).

## Next steps

* [Use skills in coding agents](/registry/skills/how-tos/use-in-coding-agents): Use a reviewed skill in Claude Code, Claude Desktop, or Codex.

## See also

* [Publish skills with aireg](/registry/skills/how-tos/publish-with-cli): Run the dry run and publish yourself.
* [Sync skills from GitHub](/registry/skills/how-tos/sync-from-github): Publish changed skills on every merge.


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