Publishing Skills

Publish a skill to your org’s private marketplace

Publishing turns a finished skill bundle into a new immutable version in your org’s Skill Library. The published version comes from the root package.json, so skill content updates and marketplace map changes require a version bump before publish. That keeps the skill private to your org: members can see and install it there, while the publish flow stays admin-only. The publish workflow stamps that root version into .claude-plugin/marketplace.json, and the publish guard rejects an out-of-date publish instead of silently reusing the previous marketplace version. If you want the versioning rules behind that behavior, see Versioning.

1. Finish the skill you want to share

  • Make sure the skill bundle is ready to ship.
  • If you are still drafting the content, start with Authoring Skills.

2. Publish it from your agent

Ask your agent: "Publish the Team QA skill for our org."

Your agent publishes a new immutable version, records it in the org library, and confirms the skill slug and version number.

{
  "scope": "org",
  "visibility": "private",
  "version": "new immutable release"
}

3. Or publish it from the dashboard

  • Open the org’s Skills page.
  • When the page opens from a project, it keeps that project context selected.
  • Use the new skill or edit flow.
  • Save the skill. The page refreshes and shows the updated version in the library.

4. Verify the publish

Ask your agent: "Show me the current version of Team QA in our org Skill Library."

If the publish worked, the skill appears with the new version number.

What private to your org means

  • The skill belongs to your organization, not to the public Gloria catalog.
  • People outside the org do not see that org’s skill library.
  • Members can install the skill from the org library after it is published.
  • If you edit an existing skill, Gloria versions it in place instead of forking a new skill under a new name.

Next