Skill source
The Source tab shows the package an agent receives when it uses a skill. A package starts withSKILL.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.mdfor its core instructionsreferences/decision-format.mdfor consistent decisionsreferences/owner-resolution.mdfor matching actions to peopletemplates/follow-up.mdfor a reusable messageexamples/product-review.mdfor 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.Sync skills from GitHub
Configure pull request preflight and protected-branch publishing for a Git-backed collection.