Skip to main content
A skill’s source is the package an agent receives when it uses the skill, together with the record of where each version came from. Read it in the Source tab to know exactly what a version contains before you adopt, release, or restore it.

Skill package

A package starts with SKILL.md, the skill’s core instructions, and can also contain references, templates, examples, scripts, and other files the job needs. Every file belongs to a specific version, and Atlan Trident shows the package size and each file’s content, so you can tell what changed between versions. Review supporting files as carefully as SKILL.md. A template or script can change what the skill sends, reads, or writes.

Provenance

The source label shows how the skill entered Atlan. A skill published from a Git repository links to its repository and commit; a skill created in Atlan Trident shows its Atlan source instead. When you publish with aireg from a Git checkout that has an origin remote, aireg records the repository and the skill’s folder with each version. The repository and path identify the skill across updates, so a later merge appends a version without losing the provenance of earlier ones. A checkout without a remote can still publish, but that version has no repository link. When the workspace already holds a skill of the same name, a publish from Git appends a version to it and keeps its history. That includes a skill created in Atlan Trident, which aireg adopts, and a skill whose folder moved within the same repository. aireg refuses the publish if the existing skill was published from another repository, or was published from Git but Atlan Trident does not name its repository.

Source tab

  • File tree: Open each file. Markdown files have a rendered preview and a source view.
  • Version header: The selected version’s name, file count, state (Released, In review, Blocked, or Archived), and when and by whom it was saved.
  • Versions: Every version, newest first. Open an earlier one to select Compare with vN or Restore as new version.

Example

meeting-notes-to-actions is published from skills/meeting-notes-to-actions in a team repository. Its version 5 package holds:
  • SKILL.md for the 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 worked example
Source shows the repository and commit for version 5, and Compare with v5 on version 4 shows that only templates/follow-up.md changed.

What source does not tell you

  • Who wrote each change. aireg does not record authors or committers; use the repository’s history.
  • Whether the package is safe. Read the version’s How skill security scans work and review supporting files yourself.
  • Which repository owns the skill as a record. The Source tab names the repository a version was published from; it does not make the repository a record. In the Atlan desktop app, you can register a source repository in a workspace under Brain > Repos, and skills, agents, and scorers can link to it. Publishing with aireg links the version to the repository record for the checkout’s remote — the one the workspace already holds, or one aireg registers in the workspace when it holds none.