Publish skills under an organization scope using the @org/name format.

Scoped Packages

Scoped packages use the @org/name format, similar to npm scoped packages. They let organizations publish skills under their namespace.

How scopes work

Scoped and unscoped names are separate — ai-commits and @myorg/ai-commits are different packages.

Create an org on the web at shipables.dev/orgs/new, or the org must already exist.

shipables login

When you run shipables publish, the CLI detects your organization memberships and prompts:

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

Select the org scope to publish as @myorg/my-skill.

You must be a member of the organization with owner or admin role
The skill name in SKILL.md frontmatter is the bare name (e.g., my-skill), not the scoped name
The scope is added during publishing based on your selection

shipables install @myorg/ai-commits

Scoped packages work identically to unscoped ones — the CLI resolves, downloads, and configures them the same way.

Organization names and usernames share the same namespace. This means:

Org names must be lowercase, alphanumeric, and can include hyphens. Max 39 characters.