> ## 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.

# Source

> Inspect a skill package, provenance, and version history.

# Skill source

The **Source** tab shows the package an agent receives when it uses a skill. A
package starts with `SKILL.md`, but it can also contain references, templates,
examples, scripts, and other files needed to do the job well. Source also holds
the skill's version picker and version comparison.

## Inspect the package

Use the file tree to open each file. Markdown files have a rendered preview and
a source view. Atlan also shows the package size and a content digest for each
file, so you can tell what belongs to the selected version.

In this example, `meeting-notes-to-actions` includes:

* `SKILL.md` for its core instructions
* `references/decision-format.md` for consistent decisions
* `references/owner-resolution.md` for matching actions to people
* `templates/follow-up.md` for a reusable message
* `examples/product-review.md` for a concrete worked example

## Check where it came from

The source label identifies how the skill entered Atlan. A Git-backed skill
links to its repository and pinned commit. Skills created in Atlan show their
Atlan source instead.

For a skill published through GitHub SkillSync, confirm the repository, commit,
repository-relative path, and available author or committer details. The
repository and path identify the source record across updates. A later merge can
append a version without losing the provenance of earlier versions.

When the checkout has usable remote Git provenance, the CLI registers or reuses
one repository artifact in the first configured workspace before it publishes
any skill. It passes that repository ID into every skill upload, linking the
repository artifact and skill artifact. Repository registration errors stop the
publish. A checkout without a usable remote can still publish, but the resulting
skill has no repository link.

<Card title="Sync skills from GitHub" icon="code-branch" href="/registry/skills/how-tos/sync-from-github">
  Configure pull request preflight and protected-branch publishing for a Git-backed collection.
</Card>

<Tip>
  Review supporting files as carefully as `SKILL.md`. A template or script can
  change what the skill sends, reads, or writes.
</Tip>

## Compare or restore a version

Use the version picker at the top of **Source** to open an earlier version. The
selected version shows whether it is live or has been superseded, when it was
released, and who released it.

When you open an earlier version, select **Compare with live** to inspect the
file changes against the current version. This comparison is always against the
live version, not another earlier release.

People with permission to update the skill can select **Restore** for an earlier
version. Confirming the action publishes a new version with that version's
files. It preserves the current version and the rest of the history.

<Warning>
  Restore changes what future users receive. Review dependencies and the live
  version first, then confirm the new version appears in **Source** before
  treating the recovery as complete.
</Warning>