Agent skills tend to spread across global folders, project folders, and
different harnesses. SelfTune inventories those locations together so you can
see what exists before deciding what to keep or change.
See the complete library
Open Skills in Desktop, or run:
The inventory distinguishes:
- identical copies installed in several places;
- same-name skills with conflicting contents;
- current skills with observed problems;
- skills that have not yet produced enough evidence; and
- protected or organization-managed skills that SelfTune must not move.
Missing usage evidence does not mean a skill is unused. SelfTune labels that
state as unobserved and asks you to measure it before removal.
Choose one canonical copy
When identical or source-confirmed copies can be consolidated, preview the
complete plan:
The plan shows the canonical revision, packages that would be archived, and
project locations that would become managed links. Ambiguous or conflicting
revisions remain untouched until you choose one explicitly.
After reviewing the plan, apply it:
SelfTune archives displaced packages instead of deleting them and records an
undo command for every decision.
Remove clutter without losing work
Quarantine a reviewed package when it should leave active agent registries but
remain recoverable:
List or restore quarantined packages later:
Restore refuses to overwrite an occupied destination.
Package skills around the work
Once the Library is understandable, create Skill Sets around project needs—not
around every skill you happen to own. A Set pins immutable revisions and can be
previewed before it is projected into Claude Code, Codex, OpenCode, Pi, or a
supported project folder.
Continue with Manage projects and Skill Sets. 
