/atlan-* commands and skills that teach a coding agent, such as Claude Code, how to publish skills, register agents, upload files, and record outputs in Atlan. They run in your own session, with your identity, and call the Atlan MCP tools on your behalf.
How your agent gets them
The same commands and skills reach your client two ways:- Atlan MCP endpoint: When your client is connected to Atlan’s MCP endpoint, each command and skill is offered as an MCP prompt named after it, such as
atlan-new-skill. Their supporting files are offered as MCP resources underatlan://defaults/. See Connect Claude Code. - The
atlanaiplugin: Atlan’s Claude Code plugin marketplace serves anatlanaiplugin that carries the same files as plugin commands and skills.
/mcp__<server>__<prompt>. With the server named atlan, as in Connect Claude Code, run:
/atlan-analytics appears only when Metrics Studio is installed. Every argument is optional.
Commands
Skills
The commands point to these skills for the full procedure. Each skill’s description says when to use it.Rules
- Your identity, your permissions. Each command acts as the signed-in identity and reaches only the workspaces that identity can access.
- Workspace choice. When you can write to more than one workspace, the command asks which one to use.
- Nothing runs in Atlan. These commands work in your client’s session. Registering an agent records it; it doesn’t deploy or run it.
- Published skills still follow release policy. A skill version created by a command is scanned and released under the workspace’s release policy. See How skill versions and releases work.
Related
- Skill package format: The rules
SKILL.mdand its package must meet. - Connect Claude Code: Connect the Atlan MCP endpoint.
- Sync skills from GitHub: What
/atlan-link-skillsets up.