How to publish skills under your organization's scope.
Publishing under an Org
Publishing under an organization creates scoped packages like @myorg/skill-name.
Requirements
- You must be a member of the organization with owner or admin role
- You must be logged in (
shipables login)
Publishing flow
- Create your skill with
shipables init(or manually createSKILL.mdandshipables.json) - The
namein your SKILL.md frontmatter should be the bare name (e.g.,my-skill, not@myorg/my-skill) - Run
shipables publish - When prompted, select the organization scope:
? Publish as:
janesmith/my-skill (personal)
> @myorg/my-skill (myorg)
- The skill is published as
@myorg/my-skill
Installing scoped skills
Users install scoped skills the same way as unscoped:
shipables install @myorg/my-skill
Who can publish updates
Any member with owner or admin role can publish new versions of org-scoped skills. This enables team workflows where multiple people can maintain and update skills.
Web publishing
You can also publish through the web at shipables.dev/publish:
- Log in
- Select your organization from the scope dropdown
- Enter the skill name
- Upload the tarball (
.tar.gz,.tgz, or.zip)
Ownership
Skills published under an org scope are owned by the organization. If a member leaves the org, they lose the ability to publish updates, but the skills remain available.