Publish skills from coding agent

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 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. 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.
Codex connected to Atlan (optional): Needed only to verify through MCP. See Connect 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. 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.

Inventory skills and preview publish

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

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.

Approve batch

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

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.

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.

Next steps

Use skills in coding agents: Use a reviewed skill in Claude Code, Claude Desktop, or Codex.

Find and share skills

Register and manage agents

Connect models and tools

Give agents business context

Observe agent runs

Evaluate and improve agents

Track agent cost

Before you begin

Troubleshooting

Next steps

See also

​Before you begin

​Troubleshooting

​Next steps

​See also

Before you begin

Troubleshooting

Next steps

See also