Skip to content
Skills Library
Management & product · Tool integration

rolebase

/rolebase

Manage the user's Rolebase account (organizations, org chart, roles, members, meetings, discussions, tasks, decisions) through the Rolebase API, with an API key read from the environment. Use when the user asks about their Rolebase organization or wants to change something in it.

Repository
rolebase ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
8
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Manage the user's Rolebase account (organizations, org chart, roles, members, meetings, discussions, tasks, decisions) through the Rolebase API, with an API key read from the environment. Use when the user asks about their Rolebase organization or wants to change something in it.

Original author description

Manage the user's Rolebase account (organizations, org chart, roles, members, meetings, discussions, tasks, decisions) through the Rolebase API, with an API key read from the environment. Use when the user asks about their Rolebase organization or wants to change something in it.

How it works

  1. Setup
  2. GraphQL
  3. tRPC
  4. When this skill is out of date
Original SKILL.md headings · 58 lines, 460 words
SKILL.md preview
---
name: rolebase
description: Manage the user's Rolebase account (organizations, org chart, roles, members, meetings, discussions, tasks, decisions) through the Rolebase API, with an API key read from the environment. Use when the user asks about their Rolebase organization or wants to change something in it.
---

# Rolebase

Before the first call, read [reference.md](reference.md): the working rules, the data model and ready-made queries. Follow its working rules, above all the approval before any write.

## Setup

- `ROLEBASE_API_KEY` (required): if it is empty, ask the user to create a key in Rolebase (**My account > API keys**) and to set it in the environment. Never ask for the key in the conversation, and never print it.
- `ROLEBASE_API_URL` (optional): defaults to `https://api.rolebase.io`. Set it for a self-hosted or local instance (`http://localhost:8888`).

## GraphQL

Reads and plain edits go through GraphQL. Pass the body through a heredoc to avoid quoting issues, and leave `variables` out rather than setting it to `null`:

```bash
curl -s "${ROLEBASE_API_URL:-https://api.rolebase.io}/graphql" \
  -H "x-api-key: $ROLEBASE_API_KEY" -H 'content-type: application/json' \
  --data @- <<'EOF'
{"query": "query ($orgId: uuid!) { member(where: { orgId: { _eq: $orgId } }) { id name } }",
 "variables": {"orgId": "<orgId>"}}
EOF
```

The response is `{"data": ...}`, or `{"errors": [{"message": ...}]}` with a 400 status.

Explore the schema with introspection on the same endpoint:

- root fields: `{ __schema { queryType { fields { name } } mutationType { fields { name } } } }`
- an object type: `{ __type(name: "task") { fields { name type { name kind ofType { name } } } } }`
- an input type: `{ __type(name: "task_insert_input") { inputFields { name type { name kind ofType { name } } } } }`

## tRPC

Business actions (create an org, invite a member, archive a role with its sub-roles, export data...) go through tRPC procedures:

```bash
# Query: GET with the input as a url-encoded JSON
curl -s -G "${ROLEBASE_API_URL:-https://api.rolebase.io}/org.isOrgSlugAvailable" \
  -H "x-api-key: $ROLEBASE_API_KEY" --data-urlencode 'input={"slug": "acme"}'

# Mutation: POST with the input as the JSON body
curl -s "${ROLEBASE_API_URL:-https://api.rolebase.io}/circle.archiveCircle" \
  -H "x-api-key: $ROLEBASE_API_KEY" -H 'content-type: application/json' \
  --data '{"circleId": "<circleId>"}'
```

The response is `{"result": {"data": ...}}`, or `{"error": {"message": ..., "data": {"code": ...}}}`.

The procedures, their type and input are listed in https://rolebase.io/en/developers/trpc-api.md and the router pages it links to (for instance https://rolebase.io/en/developers/trpc-api/members.md). Skip the internal procedures.

## When this skill is out of date

The online documentation follows every product change, this skill may lag behind. When a call fails in a way this skill or reference.md does not explain, or the API contradicts them:

1. Read the matching pages of the online documentation, from https://rolebase.io/llms.txt (add `.md` to a page URL for its Markdown version), and check the schema by introspection.
2. Carry on with the documented behavior.
3. At the end, tell the user what was out of date. If this skill is installed as a Claude Code plugin, suggest `/plugin marketplace update rolebase`. If it is a local copy, offer to fix SKILL.md or reference.md.
Files in this package (2)
  • SKILL.md 3 KB
  • reference.md 4 KB

Versions

The database has no other skills named rolebase.

Database snapshot: 13.11.2026 · package version 914614a9dd4d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100webapp-browser
    Test anything in the local Rolebase webapp with the Playwright browser, signed in as a local test admin, with few tokens. Use to check a UI change, open a page or modal, take a screenshot, or test a flow end to end in the webapp (including /admin).
  • 100newsletter
    Create, update, test or send a Rolebase email campaign to all users (product newsletter or legal information such as a change of terms or operator). Use when the user asks to write, edit, test or send a newsletter, a campaign or a legal email, or runs /newsletter.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.