SKILL.md at its root, whose front matter names the skill and says when to use it; the package format lists every field and limit. Each publish saves a new version with its source. Atlan Trident scans the version, a release decides which version people get, and traces attribute runs back to the skill and its related skills, agents, and files.

Core offerings
Find and assess skills
Check a skill’s version, source, scan, and usage before you rely on it.
Publish or update skill
Choose a publishing method: Desktop, a terminal, GitHub, or an agent.
Release skill version
Release, roll back, or withdraw the version people get.
Check security scans
Read each version’s scan decision and findings, and what blocks a release.
Review skill usage
See runs, people, agents, and success rate from attributed traces.
Improve from recorded runs
Review suggested changes based on recent runs.
Choose where to start
- New to skills? Bring skills into Atlan Trident imports the skills on your computer with Atlan Trident Desktop, then moves one to a team workspace.
- Using a skill in Claude or Codex? Use skills in coding agents.
- Deciding which workspace a skill belongs in, or whether saved versions ship on their own? Choose where skills live and Set workspace release policy.
- Retiring a skill? Archive skill.
- A publish failed or a scan blocked a version? Skill errors.
Skill improvement suggestions appear only when they’re configured for your account.
See also
- Public API: the
skill.*operations under/skill/v1/skills, and releases under/registry/v1/artifacts/{artifact_kind}/{artifact_id}/releases. - MCP reference: skill tools for agents.
- Atlan commands and skills for coding agents:
/atlan-new-skilland/atlan-update-skill.