Skip to main content

Publish skills with the CLI

Use the CLI when you want to validate a local skill before a one-off publish or when a repository manifest controls a collection of skills.

Publish one local skill

Run validation first, then inspect the publishing plan before the write:
push creates a new skill or appends a version. Unchanged content is not uploaded again. Do not use --force until you have resolved the remote change that caused the drift.

Publish repository-managed skills

Use skill publish when .atlan/package.json declares the directory, destinations, and publishing branch:
--ci disables prompts and enforces the configured branch guard. It is for a reviewed automation environment, not an interactive replacement for --dry-run.

Verify the result

Use the returned skill ID to inspect the result and its versions:
For every flag, confirmation behavior, and output field, see the full atlanai skill reference. To publish the same repository on every change to its publish branch, follow Sync skills from GitHub.