> ## Documentation Index
> Fetch the complete documentation index at: https://docs.selftune.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Install and update Skill Sets

> Install verified Set revisions through supported agent tools and keep project context current.

SelfTune keeps the Set revision separate from where it is installed. That lets
you review an update once, then choose which projects or supported agents should
receive it.

## Install into a project

Open a Skill Set in Desktop, choose the project, and review the installation
plan. The plan shows creates, unchanged destinations, missing revisions, and
conflicts before **Apply** becomes available.

From the CLI:

```bash theme={null}
selftune sets plan --set <set-name> --project /path/to/project --json
selftune sets apply --set <set-name> --project /path/to/project --json
```

On a new computer, run `selftune library sync` first when the Set is stored in
your connected Cloud or self-hosted Library. Apply downloads and verifies only
missing pinned revisions.

## Install as a Claude or Codex plugin

In Desktop, open the Set and choose **Install plugin**. Desktop detects the
official Claude and Codex CLIs on the computer and shows the host, current
plugin version, proposed Set revision, and activation instructions.

SelfTune creates a revision-addressed local plugin marketplace and delegates
registration to the host's official CLI. It does not edit Claude or Codex
registry files directly. Claude may require a plugin reload or new session;
Codex requires a new session.

The first release installs skills only. MCP capabilities remain a separate
review boundary.

## Review an update

An update is a new immutable Set revision, not an in-place rewrite. Compare the
component revisions and project plan before applying it. If the Set changes
while confirmation is open, SelfTune stops and requires a fresh review.

Workspace policy is checked again at apply time:

* **Allowed** permits a reviewed apply;
* **Approval required** keeps Apply behind an explicit confirmation;
* **Blocked** stops before project files change; and
* **Required** identifies the workspace standard.

Desktop keeps the last verified policy so a known restriction is not lost
during a temporary outage.

## Roll back

Keep the apply receipt. Rollback is limited to paths that receipt says SelfTune
owns and refuses to overwrite a destination that changed afterward.

## Success criteria

* The installed revision matches the reviewed Set revision.
* Only the selected project or host receives the Set.
* Conflicting unmanaged files are preserved.
* Host activation instructions are explicit.
* A receipt makes owned changes reversible.