Skip to main content
Relationships show how a skill connects to the other skills, agents, and files in a workspace. Check them before you change or archive a skill, because a change can affect what depends on it.

Connections

A relationship links the skill to another artifact, such as a skill it needs, an agent that uses it, or a file it relies on. Used by marks what depends on the skill. Relationships are recorded in the registry; an agent can add one with the registry__relate_artifact MCP tool, and Unlink removes one.

Possible duplicate

When Atlan Trident detects another skill that overlaps with this one, the profile shows Possible duplicate and names it. It is a prompt to compare, not a decision: compare both sources, then merge them, narrow their scope, or keep both when their jobs are genuinely different.

Relationships tab

Open Relationships to see the skill’s connections as a Graph or a List. A skill with none shows No connections yet.

Relationships across workspaces

A relationship may point at a skill in another workspace of your account. If you can’t read that workspace, the relationship is still listed, with the skill marked as not readable (is_readable: false) and none of its name or content. Opening the skill needs read access to its workspace.

Example

meeting-notes-to-actions relies on people-directory to resolve owners. Before archiving people-directory, its owner opens Relationships, sees meeting-notes-to-actions under Used by, and updates it first. Separately, the profile flags meeting-action-items as a Possible duplicate; the team compares them and archives the older one.

What relationships do not do

  • Prove a dependency is complete. Only recorded relationships appear; a skill can still rely on something nobody linked.
  • Merge or archive anything. A possible duplicate is only flagged; the decision is yours.
  • Reveal skills you can’t read. A relationship into a workspace you can’t read shows that a skill is there, not what it is.