Skip to main content
Share a Skill Set when the recipient needs a complete, reproducible skill configuration. The shared object pins every component revision and preserves license and notice files.

​
Choose the sharing path

​
Share a Pack

In Desktop or Cloud, open the Set and choose Share Pack. Review the exact revision, included skills, license expressions, access mode, and expiry before creating the link. The recipient’s preview shows those same bindings before import. Open in SelfTune Desktop opens the Set review; it does not install files. The recipient can also paste the URL under Skill Sets → Add from URL. Confirmation re-fetches the preview, verifies the response hash and every embedded package, then imports the Set into the local Library. Installation into a project remains a separate reviewed action. Owners use Skill Sets → Shared Packs to inspect active, claimed, expired, or revoked links and revoke access. Revocation prevents later downloads but does not delete a copy already imported by a recipient.

​
Share with a workspace

A Set starts as personal. When Skill Sets backup is enabled for a connected workspace, the synced Set becomes a Workspace Skill Set and members can discover the same revision after sync. Use workspace policy to control installation. Use a private share instead when one named recipient outside the workspace should receive an immutable copy.

​
Export a plugin package

Choose Export to project the exact Set revision as a supported plugin archive. The ZIP is a package artifact, not a universal install URL. SelfTune re-verifies every component and blocks the export if one no longer matches. MCP servers are not part of a Skill Set. Any MCP capability attachment requires a separate review of commands, network access, credentials, and persistent data.

​
What never happens automatically

  • Opening a Pack does not install Desktop or modify agent folders.
  • Importing a Set does not apply it to a project.
  • Sharing does not publish a discoverable Registry entry.
  • License acceptance does not imply telemetry consent.
  • A Pack token does not expose the sender’s account credential.

​
Success criteria

  • The recipient and channel are explicit.
  • The preview and downloaded object refer to the same immutable revision.
  • Every component is authorized for the chosen distribution.
  • The recipient reviews the Set before import and project installation.
  • The owner understands expiry and revocation behavior.