Skip to main content
Archive a skill when people and agents should stop discovering it. Its page, saved versions, and history remain readable, so earlier runs can still be traced to the package they used.

​
Before you begin

  • You need permission to archive records in the skill’s workspace.
  • Review the skills that depend on it and agents that use it.
  • Replace the dependency in active agents before archiving a skill they still need.
There is no restore control for an archived skill in the app. Archiving removes the skill from discovery and the workspace’s Claude Code plugin. It leaves the local folder you imported untouched.

​
Archive the record

  1. Open the skill’s profile.
  2. Open Skill actions and select Archive skill.
  3. Review the affected skills and agents in the confirmation dialog. If their dependencies cannot be read, check them before proceeding.
  4. Select Archive.
  5. Confirm the success message and check that the skill leaves the active skill list.
In a personal workspace, this affects your skill registry. In a shared workspace, members stop finding the skill in the workspace’s list and plugin. Already copied local files stay on disk.

​
If archive is unavailable

The dialog refuses to archive a system skill or a skill blocked by a security scan. Only Atlan can retire a system skill. For a blocked skill, fix the finding and wait for a passing scan before archiving it. See Skill security scans. If the menu says you do not have permission, ask the workspace administrator to review your access.

​
Keep a skill available with an earlier release

If the current package has a regression but the skill should remain available, roll back its release instead of archiving the whole record.