Skip to main content

​
Publish skills through Claude Code

Use Claude Code when the skill folders are already in the repository you are working in and you want an agent to prepare the batch. MCP writes Registry artifacts. It does not install the resulting skills into Claude Code.

​
Before you start

Connect Claude Code to Atlan MCP and confirm that the target workspace is available to your identity. See Claude Code for setup and connection checks. The skill folders must be available in the repository. Each one needs a SKILL.md file. Do not ask an agent to upload secrets, customer data, or files outside the skill packages.

​
Start a session and inventory

Start with session setup and read-only discovery. The session is recorded for review, but the request does not create or change a skill:
Review the list, the target workspace, and any naming conflicts. The live MCP tool list and schemas returned to Claude Code are authoritative.

​
Confirm the batch

Only after the inventory is correct, send a bounded confirmation:
registry__create_artifacts writes state and runs the skill kind’s create hooks. One rejected item does not roll back skills that succeeded, so inspect each returned result before continuing.

​
Verify and use the skill

Open each created skill in Atlan and confirm its version and source files. A Registry skill is not installed into Claude Code just because MCP created it. Use the selected-skill handoff after review when you want to use a skill in a Claude Code task.

Use a skill in Claude Code

Hand a reviewed skill to Claude Code from its Atlan profile.