| name | rote-org |
| description | Manage rote registry organizations — create / delete an org, list and change member roles, invite or remove users, revoke or list pending invites, view plan and usage, and manage org SSO. Use when the user says things like "create an org", "invite teammate to my org", "list org members", "remove user from org", "change role", "revoke invite", "what's my org usage", "set up SSO", "verify an SSO domain", or otherwise references organization administration in rote. |
rote-org — Organization management
All rote-<name> references in this document — including every name in the Handoff
Contract — are companion skills, never CLI commands (rote-shell is not rote shell).
Invoke them through the runtime's skill mechanism; only literal rote … commands run in a
terminal.
All operations go through rote registry org <subcommand>. These commands handle auth, validation, and error rendering.
Login first: rote login (auth is shared with the main rote skill).
Run one org command at a time, read the result before deciding the next action, and never assume
membership, role, quota, or pending-invite state from memory. Use the base rote companion skill
only when a caller needs the full workflow graph.
Roles: admin | developer | reader. Invite default role: developer.
Slug = URL-safe org identifier (e.g. my-org). --help calls this <org> for invite/members commands and <slug> for the rest — same thing.
Handoff Contract
- Use when: the user asks to create, delete, inspect, invite to, remove from, change roles in, or
view plan/usage for a rote registry organization.
- Preconditions: the user is authenticated or login is surfaced as the blocker; target org slug and
requested admin operation are known; destructive deletes and privileged role changes are explicitly
confirmed.
