Sherpi
Concepts

Orgs and Roles

How teams, permissions, and review flows work in Sherpi.

Sherpi organises everything around orgs. Your org is auto-created when you first log in (or you join an existing one via an invite).

Roles

RoleCan do
AdminEverything — manage settings, members, review queue, publish skills
MemberCreate, publish, and install skills. Can see their own submissions.

Skill lifecycle

draft → in review → (approved) → published → installed
  • Draft — authored locally, not yet shared
  • In review — uploaded to the org, waiting for admin approval
  • Published — available to install by any member
  • Installed — running in a member's editor

Auto-publish

Admins can enable auto-publish in org settings. When on, published skills go live immediately without admin review. Useful for small, trusted teams.

When auto-publish is off, every publish lands in the review queue at /review in the web app.

Toggle it from the CLI:

sherpi org settings get
sherpi org settings set auto-publish false   # require admin review
sherpi org settings set auto-publish true    # publish immediately

Or from the web app under Settings → General.

Review queue

Admins see submissions in the web app and can:

  • Approve — publish the skill
  • Reject — send it back with a note
  • Delete — remove the submission

Authors can re-edit and re-publish after a rejection.

On this page