Skip to main content
Use Codex when the skill folders are already in the repository and you want an agent to inspect them before publishing. Registry’s current MCP tools are read-only. Publish with the Atlan CLI, then use MCP to verify the result.

​
Before you start

Install and authenticate the Atlan CLI. Connect Codex to Atlan MCP if you also want post-publish verification. See Codex for connection checks. Project-level MCP configuration loads only after Codex trusts the project. The skill folders must be available in the repository. Each one needs a SKILL.md file. Do not ask Codex to upload secrets, customer data, or files outside the skill packages.

​
Start a session and inventory

Ask Codex to validate the local skills and show the CLI dry run:
Review the plan, target workspace, and any naming conflicts.

​
Confirm the batch

Only after the dry run is correct, approve the CLI write:
Follow Publish skills with the CLI for the validation, dry-run, and publish commands.

​
Verify and use the skill

Open each published skill in Atlan and confirm its version and source files. Then initialize an MCP session, search for the skill, and read it by the handle returned from search. A Registry skill is not installed into Codex merely because it was published.

Use skills with Codex

Find and inspect skills through Codex with the Atlan MCP connection.