Skip to main content
Every publishing method writes a skill and its package into one workspace, where Atlan Trident scans it and serves it under the workspace’s release policy. The methods differ in where the skills live, how often they change, and who reviews them. None installs a skill into Claude Code or Codex.

Methods compared

To publish to a registry you host yourself rather than to Atlan Trident, use aireg publish from Registry OSS.

Core offerings

Bulk upload skills in Desktop

Import many local skill folders into one workspace.

Publish skills with aireg

Preview and publish from a terminal.

Sync skills from GitHub

Publish changed skills on every merge to a protected branch.

Release skill version

Choose which saved version Atlan Trident serves, or roll back.

Package and verification checklist

Whatever the method, prepare each package the same way:
  1. Put SKILL.md at the package root, with only the references, templates, examples, scripts, and small assets the skill needs.
  2. Remove secrets, customer data, and private source material.
  3. Choose the workspace. Keep an early skill in your personal workspace, and publish to a shared workspace only when a team needs to find or maintain the same record. See Choose where skills live.
After publishing, open the skill profile and confirm on Source that the version, file list, and source details are what you sent, and on Security that its scan passed. Publication has not succeeded until the version is discoverable in the intended workspace.
A published version is served only after its security scan and any review pass, and only under the workspace’s release policy. To correct a release, publish a fixed package, or roll back from the versions list on the skill’s Source tab; see Release skill version.

See also