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

# Relationships

> Understand dependencies, duplicates, and conflicts between skills.

# Skill relationships

Relationships explain how a skill fits with the rest of a workspace. Open the
**Relationships** tab to see declared dependencies, downstream dependents, and
AI-inferred duplicate or conflict candidates.

## Relationship types

| Relationship | What it means                                              | Example                                                                                                                       |
| ------------ | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Dependency   | This skill needs another skill to finish its job.          | `meeting-notes-to-actions` depends on `people-directory` to resolve owners and `calendar-context` to add the meeting details. |
| Dependent    | Another skill needs this one.                              | `weekly-planning` uses open actions created by `meeting-notes-to-actions`.                                                    |
| Duplicate    | Two skills are trying to solve substantially the same job. | `meeting-action-items` and `meeting-notes-to-actions` both turn notes into decisions, owners, and follow-ups.                 |
| Conflict     | Two skills give opposite guidance in the same situation.   | `instant-follow-ups` says to send immediately, while `meeting-notes-to-actions` asks for confirmation before sending.         |

## Use relationship signals

Dependencies and dependents are explicit links. Review them before updating or
archiving a skill because a change can affect the skills downstream.

Possible duplicates and conflicts are review prompts, not final decisions.
Compare both sources, decide whether to merge or clarify their scope, and keep
separate skills when their jobs are genuinely different.