Publish or share 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

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

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:

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.

Start here

Use SelfTune

Run it your way

Concepts

Reference

Publish or share a skill

Choose a path

Ask your agent

Verify before publishing

Success criteria

​Choose a path

​Ask your agent

​Verify before publishing

​Success criteria

Choose a path

Ask your agent

Verify before publishing

Success criteria