Skip to main content
Publishing creates a reviewed, immutable Skill Set release for your Team workspace. It is different from installing a Set on this computer or sending an expiring share link.
A Skill Set is a reusable collection of exact Agent Skill revisions. In plain language, it is a named set of instructions your supported AI tools can use together.

​
Before you publish

Open the Skill Set in Desktop and choose Publish to team. SelfTune shows:
  • the Set name and purpose;
  • every included skill and its exact revision;
  • supported AI tools;
  • license information;
  • whether the portable release and pinned revisions passed their checks; and
  • which information will leave this computer.
Publishing does not start from a name alone. The confirmation is bound to the exact Skill Set revision and portable release object you reviewed. If either changes before the upload begins, SelfTune stops and asks you to review again.

​
What leaves your computer

After you explicitly confirm, Desktop uploads one canonical portable Skill Set envelope. It contains the exact packaged skill revisions and the bounded metadata needed to verify them. Cloud derives and checks the object hash before creating the release. The upload does not include local paths, project or folder names, prompts, conversations, sessions, raw evaluations, improvement traces, or an automatic copy of the rest of your Library.

​
Review the release in Cloud

Open Published Skill Sets in Cloud to see releases from the active Team workspace. The list and detail pages show purpose, release number, publication date, publisher, components, target AI tools, license summary, readiness, and provenance. Hashes are available under technical details. Published release contents are read-only. From the release detail page, a Team owner or admin can separately assign the exact release to a teammate’s linked computer. The recipient still reviews and confirms the local installation. Sending a share link remains another action with its own confirmation and access rules.

​
Immutable retries

Publishing the exact same reviewed revision again returns the existing release instead of replacing its bytes. Reusing a publication attempt with different bytes is rejected as an integrity conflict. A changed Set becomes a later release; an existing release is never edited in place.