> ## 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.

# Publish or share a skill

> Choose a distribution path and review what leaves your machine before sharing a skill.

Publishing changes the trust boundary. Decide who should receive the skill,
which revision they receive, and whether evidence or metadata travels with it.

## Choose a path

| Goal                             | Path                       | Remote account required   |
| -------------------------------- | -------------------------- | ------------------------- |
| Install in another local project | Skill Set                  | No                        |
| Share source with collaborators  | Git repository             | Depends on repository     |
| Distribute a versioned skill     | Remote Library or registry | Yes                       |
| Operate your own shared library  | Self-host                  | No SelfTune Cloud account |

## Ask your agent

```text theme={null}
Prepare <skill-name> for <local project / Git repository / Remote Library>.
Verify the exact revision first and show me every file and metadata field that
will leave this machine. Do not publish, push, create credentials, or overwrite
an installed copy until I approve the destination and contents.
```

## Verify before publishing

```bash theme={null}
selftune verify --skill-path /path/to/skill
```

Review the package for secrets, local paths, user data, generated artifacts,
and unsupported dependencies. Confirm that the validation report refers to the
same revision you intend to share.

For a local publish workflow, the intent-level command is:

```bash theme={null}
selftune publish --skill-path /path/to/skill
```

Remote Library and registry operations have separate authentication and upload
steps. Use their reference pages only after choosing that data boundary.

## Success criteria

* The destination and recipients are explicit.
* The shared revision is immutable or versioned.
* The package contains no secret, raw transcript, or unintended local file.
* The user approves the final contents and remote action.
* Installation or rollback instructions accompany a distributed revision.

Treat verification, local installation, source push, registry publication, and
remote-library upload as separate mutations. Show the exact revision and file
manifest. Scan for credentials and unintended user data. Stop for explicit
approval immediately before any remote write or replacement of an installed
skill.