Skills

Find, assess, use, and improve reusable skills.

Skills

A skill is a reusable package of instructions and supporting files for a specific job. It gives a team one record for the instructions it relies on, the version an agent received, and the evidence available after use.

Use a skill profile to answer four practical questions before you adopt or change it:

1. Does it fit this job? Read the summary, prerequisites, and trigger guidance.
2. Can I trust this version? Review its source, owner, and version history.
3. What else does it affect? Check dependencies and relationship signals.
4. Is it helping? Review the available usage evidence and linked runs.

Skill names are unique within a workspace. Use a name that describes the job, such as meeting-notes-to-actions, rather than the team or person who created it. The same name can be used in another workspace.

Read every skill surface

Surface	Use it to	Availability
Overview	Check what the skill does, when it applies, prerequisites, source-file count, and the activity summary.	Available for every skill you can open. Run metrics populate after recorded use.
Source	Read the package files, provenance, and version history.	Available when the package is visible to you.
Relationships	Review declared dependencies and dependents, then assess duplicate or conflict candidates.	Available when relationship data exists.
Usage	Review trace-backed runs, models, tools, people, versions, and linked traces.	Available only when attributable execution data exists.
Security	See the planned scan, findings, trend, and release-gate experience.	Coming soon. It is not a scan result.

Select Overview first, then move to the surface that answers the question you have. Do not treat an empty activity panel as a quality result or a missing Security result as a passed review.

Follow a skill from discovery to improvement

Start in the workspace where the skill should be visible. Browse or search for the skill, open its profile, then choose the next action that matches your job.

Discover and use a skill

Find the right skill, assess its current version, and open it in a supported environment.

Publish and version a skill

Prepare a package, publish it into the right workspace, and verify the new version.

Inspect the record

Source and versions

Inspect the package, compare an earlier version with live, or restore one safely.

Security

See what the planned security review will cover. It is not a scan result yet.

Relationships

Check dependencies and review possible duplication or conflicting guidance.

Usage

Interpret the trace-backed activity that Atlan can attribute to the skill.

Choose the right workspace

Keep an early or personal skill in your personal workspace. Move to a shared workspace when a team needs the same record, a clear owner, or its own access boundary. The source stays attached to the skill record; publishing it into a shared workspace does not remove its local source.

Choose a workspace for a skill

Compare personal and shared scope before publishing or sharing a skill.