Skip to main content
Sharing and publishing are different trust boundaries. Start with the outcome, then choose the narrowest channel that serves it.

​
Prefer a Skill Set for complete workflows

A Skill Set preserves the exact combination and revisions that belong together. Use Share Skill Sets securely for Packs, workspaces, private shares, and plugin exports.

​
Publish an individual skill

Use the Registry only when an individual skill should be discoverable and versioned independently.
Before the remote write, review the complete package—not only SKILL.md—for scripts, references, assets, secrets, local paths, user data, licenses, and notices. Confirm that verification and publication refer to the same revision. Export, local installation, source push, remote upload, private sharing, and Registry publication are separate actions. License acceptance, lifecycle status, and contributor signals are also separate choices. Read Skill distribution, licensing, and signals for the detailed policy or use the agent distribution playbook.