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

1. Create your skill with shipables init (or manually create SKILL.md and shipables.json)
2. The name in your SKILL.md frontmatter should be the bare name (e.g., my-skill, not @myorg/my-skill)
3. Run shipables publish
4. When prompted, select the organization scope:

? Publish as:
    janesmith/my-skill (personal)
  > @myorg/my-skill (myorg)

5. 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:

1. Log in
2. Select your organization from the scope dropdown
3. Enter the skill name
4. 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.