Skip to main content
Finding and assessing a skill in Atlan Trident gives you the skill that fits your job in the right workspace, with its released version, source, security scan, and usage checked before you rely on it. Use it whenever you need a skill for real work rather than a similar-looking name from another workspace. From a coding client, you can find skills from Codex or connect Claude Code instead.

Before you begin

Before you start, make sure you have:
  • Workspace access: Access to the workspace where the work belongs. A skill appears in a workspace’s Skills listing only in workspaces you can open.
1

Find skill

  1. Open the workspace from the sidebar.
  2. Select Skills in the sidebar and use Search skills to find the skill by name or description.
  3. Select the skill to open its profile.
To search across the whole app instead, press ⌘K.
2

Assess skill

Read the profile tabs in order:
  1. Overview: What the skill does, when to use it, prerequisites, and triggers. The Security card states the scan’s verdict — Safe to install, Caution, Do not install, or Not scanned yet — and, once a scan has run, a Details, Review, or See why button opens the Security tab. When the newest version’s own scan has not finished, the verdict says which version it is for, and a note says the newest one is out and waiting for its scan. The Activity card shows the last 30 days’ Runs, People, Releases, and Security scans, each opening the tab that holds it.
  2. Source: The package files and provenance of each version. Confirm which version shows Live: that is the one Atlan Trident serves.
  3. Releases: Every release of the skill. A skill installed from the Store has no Releases tab — its versions are on Source.
  4. Store: The skill’s Store listing, when the Store lets your organization publish skills.
  5. Usage: Trace-backed runs, when attributable evidence exists.
  6. Improve: The changes editors can apply from recent runs, and Skill quality when a judged check is available.
  7. Security: The latest scan’s decision, findings, and history.
  8. Relationships: Dependencies and nearby skills that could overlap with it.
  9. Settings: Who owns the skill, which version is live, and its lifecycle state.
Beside Share at the top of the profile, the avatar stack opens Recent activity: who read or used the skill in the last 30 days, each person’s most recent read or run, and which coding agent a run came from. Depending on your role, reads may be limited to your own, so no stack doesn’t mean nobody is using the skill.
3

Use skill

Choose how your environment takes the skill:
  • Claude Code or Claude Desktop: Select Open in to hand the skill over as a prefilled prompt. See Use skills in coding agents.
  • Codex: Codex has no Open in handoff; ask Codex to find the skill through MCP. See Use skills in coding agents.
  • Pinned package: Download that version’s bundle with GET /skill/v1/skills/{skill_id}/versions/{version_ordinal}/bundle or client.skills.versions.get_bundle(). See Retrieve pinned version. aireg installs the release Atlan serves and cannot pin an earlier version.
  • Every session: On the In your Brain card on the profile, turn on Always ready to load the skill in every session, or leave it off to keep it one search away; Remove from Brain takes it out of your setup. See Choose what your AI tools load.
Do not assume a skill works in every harness. Add environment-specific setup only after testing it against the current product and client version.
4

Verify version in use

Confirm that your environment received the skill you assessed: the prompt names the skill you reviewed. If you use Copy agent prompt from Open in instead, paste it into your agent and check the same.

Search Skills list

To look through skills rather than search the whole app, select Skills in the sidebar. It lists the skills in the scope picked at the top of the sidebar: one workspace, or all of yours.
  • Filter: Filter narrows the list by workspace, or by Release — Released or Unreleased, each with its count beside it.
  • Rows: Each row shows the skill, its Author, its Runs (30d), its Workspace when the list spans several workspaces, its Status, and the timestamp for the chosen sort. Runs (30d) counts the skill’s runs in the last 30 days: a skill nobody ran shows 0, and a count Atlan could not read shows a dash. Selecting the author opens their profile; a skill with no author on record shows a dash.
  • Status: The Status column shows Live, or the chip for why the skill is not live yet: Blocked, In review, or Unreleased, with the reason under it — Checks or approval under In review, Not released yet under Unreleased. On a Blocked row, See why opens the latest scan’s most serious findings, where they fired, and Open the Security tab for all of them.
  • Sort order: Sort by Last updated, Recently created, or Name A-Z. The column headers sort by name or by time and reverse the order when selected again; Recently created is only in the sort menu, and while it is the sort the time column reads Created. While the search field has text in it, the list is ranked by relevance instead, in the same order a ⌘K search returns: the sort menu reads Sorted by relevance and the column headers do not sort, and the sort choice applies again once you clear the search. When nothing in the list contains the search text, a note above the rows says so — No name or description here contains ”…” — and the rows shown are the closest matches. When the search leaves nothing to show at all and you can add skills in the scope, the page offers Write ”…”, which names the skill after your search and opens the new-skill form with that name filled in. Needs attention, beside All above the list, lists the skills a security scan blocked or that wait on checks or an approval; it is shown only while something needs attention, or while you are on that view.
  • Keyboard: j and k move through the rows and Enter opens the focused skill; from a focused row, the arrow keys also step. Press / to move to the search field, or ? to see every keyboard shortcut.

Troubleshooting

If Open in does not open your client, see Claude does not open from Open in. For other skill errors, see Skill errors.

Next steps

See also

  • Security: Read a skill’s scan decision and findings.
  • Workspace home: What a workspace’s home shows, and where its listings are.