Skip to main content

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.

Manage versioned skill distribution across your team. Push skill folders to the cloud, install from the registry, sync to latest versions, and rollback when things break.
Registry push, install, and rollback require the Pro plan or higher. The shared installation map and broader team oversight surfaces are still strongest on Team.

​
Commands

​
registry push

Archive the current skill folder and push it as a new version. 
selftune registry push [name] [--version=<semver>] [--summary=<text>]
Run from inside a skill directory (must contain SKILL.md). The entire folder is archived — SKILL.md, scripts, assets, references.
FlagDescription
--version=<semver>Explicit version (default: auto-generated)
--summary=<text>Change summary for this version

​
registry install

Download and install a skill from the registry. 
selftune registry install <name|github:owner/repo[@ref][//path]> [--global]
FlagDescription
--globalInstall to ~/.claude/skills/ (available everywhere)
Default install path: .claude/skills/<name>/ in the current project. GitHub installs use your local git credentials and do not require a cloud registry entry: 
selftune registry install github:acme/reviewer
selftune registry install github:acme/skills//reviewer
selftune registry install github:acme/skills//[email protected] --global
  • If the repo contains exactly one SKILL.md, selftune installs it automatically.
  • If the repo contains multiple skills, selftune reports the available paths and asks for //path.
  • Direct GitHub installs are not tracked by registry sync because they bypass the cloud registry.

​
registry sync

Check all installed entries for updates and pull latest versions. 
selftune registry sync
Uses lightweight hash comparison — only downloads archives when the version hash differs.

​
registry status

Show installed entries with version drift. 
selftune registry status
Output shows each installed skill, its current version, the latest available version, and whether it’s up to date or behind.

​
registry rollback

Rollback a skill to a previous version. 
selftune registry rollback <name> [--to=<version>] [--reason=<text>]
FlagDescription
--to=<version>Target a specific version (default: previous)
--reason=<text>Record why the rollback happened
After rollback, team members should run selftune registry sync to get the reverted version.

​
registry history

Show version timeline for a skill. 
selftune registry history <name>
Displays each version with its status (current, previous, rolled back), pass rate, session count, and push date.

​
registry list

Show all published entries in the org’s registry. 
selftune registry list

​
Output format

All registry commands output JSON for agent consumption: 
{
  "success": true,
  "name": "deploy",
  "version": "1.2.0",
  "files": 8,
  "size": 4096
}

​
Local state

Installation state is tracked at ~/.selftune/registry-state.json. This file maps entry IDs to installed version hashes and paths, enabling the lightweight sync check.

​
Prerequisites

  • Authenticated via selftune alpha upload (API key configured)
  • Push/rollback: Pro plan + admin role
  • Install: Pro plan or higher