> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the atlanai CLI; `atlanai --map json` prints its command map. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.

# Manage skill packages

> Install repository-managed skill dependencies and wire the git pre-push publishing hook.

The package commands automate dependency resolution, hook wiring, and CI publishing for teams that keep skills in a Git repository. `skill install` reads `.atlan/package.json`, verifies each skill's registered digest, copies resolved skills into `.atlan/skills`, and creates native links for configured coding agents. Run it before the agent builds its skill inventory so it starts with the correct resolved set.

## Before you start

* Confirm the CLI is installed and `atlanai doctor` passes. See [Install atlanai CLI](/tools/cli/how-tos/install).
* Authenticate and confirm `atlanai auth status` shows the expected account.
* Confirm a `.atlan/package.json` manifest exists at the repository root. For the manifest format and lockfile schema, see [Sync skills from GitHub](/registry/skills/how-tos/sync-from-github).

## Install package

Reads `.atlan/package.json`, verifies registered digests, and copies resolved skills into `.atlan/skills`. Creates native links for each configured coding agent so it picks up the correct skill set on the next start.

```bash theme={null}
atlanai skill install
```

If the lockfile is missing or out of date, `skill install` reports the conflict and stops. Resolve the lockfile before retrying.

## Publish changed skills

Publishes only skills whose source changed since the given commit. `skill publish` runs non-interactively and is safe to use in CI without a confirmation prompt. Use it in a post-merge job to keep the Registry in sync with the repository.

```bash theme={null}
atlanai skill publish --changed-since HEAD~1
```

Use a trusted base commit — typically `HEAD~1` for a post-merge job or the merge base for a pull request job. Keep `--prune` opt-in: it archives Registry skills that no longer have a corresponding source file.

## Install hooks

Installs the configured git pre-push hook for automated skill publishing. The command owns only its managed hook entries and does not remove unrelated configuration.

```bash theme={null}
atlanai skill hooks install
```

After installing, test the hook by running `git push` from the repository root with a pending skill change.

For the full manifest format, lockfile schema, GitHub Action template, and CI workflow examples, see [Sync skills from GitHub](/registry/skills/how-tos/sync-from-github).

## Troubleshooting

For errors from `skill install`, `skill publish`, or `skill hooks install`, see [Skill operation errors](/tools/cli/troubleshooting/skill-operation-errors).

## Next steps

* [Automate workflows](/tools/cli/how-tos/api-automation): Script skill publishing and other CLI tasks non-interactively in CI.

## See also

* [Sync skills from GitHub](/registry/skills/how-tos/sync-from-github): Manifest, lockfile, and CI workflow for repository-managed skills.
* [Inspect and restore skills](/tools/cli/how-tos/skills-inspect): Confirm published skills and version history.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.