SKILL: Bohrium Project Management

intent

manage projects on the bohrium platform, the organizational containers for nodes, jobs, images, and datasets. use this skill when a user asks to create, list, delete, or rename projects; manage project members and their roles; or set cost limits and budgets. prefer the bohr CLI for basic operations (create, list, delete); fall back to the API only for advanced operations the CLI doesn't support (member management, cost limits, renaming). projects are the basic unit for team collaboration and cost management on bohrium.

inputs

bohr CLI (preferred for basic operations):

• bohr CLI installed on local machine or in task environment. installation scripts available for macOS and Linux; source ~/.bashrc or ~/.zshrc after install.
• no authentication required once CLI is installed and linked to user account.

API-based operations (for member management, renaming, budget adjustments):

• ACCESS_KEY environment variable or apiKey in config. obtain from bohrium account settings at open.bohrium.com.
• base URL: https://open.bohrium.com/openapi/v1/project
• HTTP headers: {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"} for POST/PUT; {"accessKey": YOUR_ACCESS_KEY} for GET.
• network connectivity to open.bohrium.com (API calls may timeout or fail if bohrium service is unreachable or rate-limited; default rate limit is not documented).

context:

• project ID (numeric, e.g. 154) for operations on existing projects.
• user role in project (creator, admin, or member) determines which operations are permitted; creators can delete or rename; admins can add/remove members, adjust budgets, but not delete projects.
• member email addresses for adding users; member userIds for removing or promoting/demoting admins.

procedure

list projects

1. Input: none (uses current bohr CLI context).
2. Step 1: run bohr project list to list projects in table format, or bohr project list --json for JSON format, or bohr project list --csv for CSV format.
3. Output: table, JSON, or CSV containing projectId and name fields. JSON response includes items: [{projectId, name, ...}].

create project

1. Input: project name (required); monthly cost limit (optional); total cost limit (optional).
2. Step 1: run bohr project create -n "project-name" to create a project with no cost limits (default "unlimited").
3. Step 2 (optional): append -m <amount> to set a monthly cost limit, e.g. bohr project create -n "my-experiment" -m 5000.
4. Step 3 (optional): append -t <amount> to set a total cost limit, e.g. bohr project create -n "my-experiment" -t 10000.
5. Output: CLI confirms project creation and returns projectId. newly created project appears at end of project list.

delete project

1. Input: projectId (numeric).
2. Step 1: confirm user role is creator (only creators can delete projects; admins and members cannot).
3. Step 2: run bohr project delete <projectId>, e.g. bohr project delete 154.
4. Step 3: CLI prompts for confirmation; acknowledge to proceed.
5. Output: CLI confirms deletion. all jobs, nodes, images, and datasets under the project are permanently removed and cannot be recovered.

rename project (API only)

1. Input: projectId (numeric), new project name (string), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator or admin (only creators and admins can rename projects).
3. Step 2: invoke POST https://open.bohrium.com/openapi/v1/project/set_name with JSON body {"projectId": 154, "name": "new-name"} and headers {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"}.
4. Step 3: check HTTP response status (200 = success, 4xx = client error such as missing accessKey or invalid projectId, 5xx = server error).
5. Output: API returns HTTP 200 on success; project name updated in project list.

view project members (API only)

1. Input: projectId (numeric), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator or admin (only creators and admins can view project members; members cannot).
3. Step 2: invoke GET https://open.bohrium.com/openapi/v1/project/{projectId}/users with headers {"accessKey": YOUR_ACCESS_KEY}.
4. Step 3: parse JSON response {items: [{userId, userName, email, projectRole, cost, ...}]} where projectRole 1 = creator/admin, 3 = regular member.
5. Output: JSON list of members with userId, email, role, and cumulative cost for each.

add project member (API only)

1. Input: projectId (numeric), target user email (string), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator or admin.
3. Step 2: verify target email is registered on bohrium (no validation endpoint; operation fails silently if email doesn't exist).
4. Step 3: invoke POST https://open.bohrium.com/openapi/v1/project/add_user with JSON body {"projectId": 154, "email": "user@example.com"} and headers {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"}.
5. Step 4: check HTTP response status.
6. Output: API returns HTTP 200 on success; user is added to project with default role "member". if email doesn't exist, API returns success but member is not actually added.

remove project member (API only)

1. Input: projectId (numeric), userId (numeric), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator or admin.
3. Step 2: obtain correct userId via GET /{projectId}/users if not known.
4. Step 3: invoke POST https://open.bohrium.com/openapi/v1/project/del_user with JSON body {"projectId": 154, "userId": 12345} and headers {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"}.
5. Step 4: check HTTP response status.
6. Output: API returns HTTP 200 on success; member is removed from project and can no longer access project resources. removed member can be recovered via recovery endpoint within a window (window duration not specified).

promote member to admin (API only)

1. Input: projectId (numeric), userId (numeric), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator (only creators can promote/demote admins; admins cannot).
3. Step 2: obtain userId via GET /{projectId}/users.
4. Step 3: invoke POST https://open.bohrium.com/openapi/v1/project/manager/add with JSON body {"projectId": 154, "userId": 12345} and headers {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"}.
5. Step 4: check HTTP response status.
6. Output: API returns HTTP 200 on success; user is promoted to admin role. admin can now add/remove members, adjust budgets, and manage project resources.

demote admin to member (API only)

1. Input: projectId (numeric), userId (numeric of current admin), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator.
3. Step 2: obtain userId via GET /{projectId}/users.
4. Step 3: invoke POST https://open.bohrium.com/openapi/v1/project/manager/del with JSON body {"projectId": 154, "userId": 12345} and headers {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"}.
5. Step 4: check HTTP response status.
6. Output: API returns HTTP 200 on success; admin is demoted to member role. user loses ability to add/remove members and adjust budgets.

set project cost limit (API only)

1. Input: projectId (numeric), cost limit (numeric in currency units, e.g. ¥), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator or admin.
3. Step 2: invoke POST https://open.bohrium.com/openapi/v1/project/set_cost_limit with JSON body {"projectId": 154, "costLimit": 5000} and headers {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"}.
4. Step 3: check HTTP response status.
5. Output: API returns HTTP 200 on success; project total cost limit is updated. when total project cost exceeds this limit, members can no longer submit new jobs or start new nodes.

get detailed project list (API only)

1. Input: ACCESS_KEY environment variable set.
2. Step 1: invoke GET https://open.bohrium.com/openapi/v1/project/list with headers {"accessKey": YOUR_ACCESS_KEY}.
3. Step 2: parse JSON response {items: [{id, name, totalCost, monthCost, userCount, projectRole, ...}]}.
4. Output: JSON list of all projects the user is member of or creator of, including cost metrics and member count.

recover deleted member (API only)

1. Input: projectId (numeric), userId (numeric of deleted member), ACCESS_KEY environment variable set.
2. Step 1: confirm user role is creator or admin and member was recently deleted (recovery window not documented; assume 30 days).
3. Step 2: invoke PUT https://open.bohrium.com/openapi/v1/project/{projectId}/recovery_user with JSON body {"userId": 12345} and headers {"accessKey": YOUR_ACCESS_KEY, "Content-Type": "application/json"}.
4. Step 3: check HTTP response status.
5. Output: API returns HTTP 200 on success; deleted member is restored to project with previous role and budget allocation.

decision points

use bohr CLI vs. API:

• if task is to create, list, or delete projects: use bohr CLI (simpler, no auth setup required beyond CLI link).
• if task is to rename project, manage members, adjust budgets, or view detailed project info: use API (bohr CLI does not support these operations).

member operation permission checks:

• if user is creator: permit all operations (create, delete, rename, add/remove members, promote/demote admins, adjust budgets).
• if user is admin: permit add/remove members, adjust budgets, view members, but NOT delete project or promote/demote admins.
• if user is member: permit none of the above; member can only view project resources and submit jobs (job submission is not covered by this skill).

project creation with cost limits:

• if user provides no cost limits: create project with "unlimited" budget (default).
• if user provides monthly limit only: set -m <amount> flag.
• if user provides total limit only: set -t <amount> flag.
• if user provides both: set both -m <amount> and -t <amount> flags.

project member budget allocation:

• if creator/admin chooses "even split": divide total project budget equally among all members via manual API calls to set individual limits (no bulk "even split" endpoint exists; creator must calculate and call API per member).
• if creator/admin chooses "uniform": set same limit for all members via repeated API calls.
• if creator/admin chooses "manual": set different limits per member via repeated API calls (no batch endpoint).

API authentication failure:

• if ACCESS_KEY is missing or invalid: API returns 401 (unauthorized) or 403 (forbidden). retry with correct key or obtain new key from open.bohrium.com account settings.
• if accessKey is not provided in headers: API returns 400 (bad request) or 404 (not found for v1 accessKey).

member addition edge cases:

• if target email does not exist on bohrium: API returns HTTP 200 (false positive) but member is not added. no validation occurs; verify member was added by calling GET /{projectId}/users.
• if target email is already a member of the project: API returns HTTP 200 but no duplicate entry is created (idempotent behavior assumed).

project deletion irreversibility:

• if user deletes a project: all jobs, nodes, images, datasets, and shared resources are permanently removed. no recovery endpoint exists for deleted projects (recovery endpoint only works for deleted members, not projects).

rate limiting and network errors:

• if API calls fail due to network timeout (default timeout not specified): retry with exponential backoff (e.g. 1s, 2s, 4s).
• if API returns 429 (rate limit exceeded): wait before retrying (rate limit window not documented).
• if bohrium service is down (5xx errors): wait before retrying.

cost tracking:

• costs incurred by members are charged to the project creator's account balance, not member accounts. if creator's balance reaches zero, no new jobs can be submitted by any member in any project.
• account balance is deducted every 5 minutes. if balance drops below threshold (default ¥100), warning email is sent.

quota enforcement:

• if user has already created 4 projects and tries to create a 5th: API rejects with error (only 4 self-created projects per user; joined projects do not count toward this limit).
• if project already has 10 custom images and user tries to create an 11th: image creation fails (not covered by this skill; see image management skill).
• if user has 100 concurrent running jobs and tries to submit a 101st: job submission fails (not covered by this skill).

output contract

bohr CLI operations (list, create, delete):

• output is human-readable table, JSON, or CSV format.
• JSON format: {items: [{projectId, name, ...}]} for list; plain projectId for create; null/empty for delete.
• success code: CLI exits with code 0. failure: CLI exits with code 1 or higher and prints error message to stderr.

API operations (all):

• HTTP response status 200 (or 201 for create-like operations): operation succeeded.
• HTTP response status 4xx (400, 401, 403, 404): client error; check request body, headers, projectId, or userId.
• HTTP response status 5xx: server error; retry later.
• response body is JSON; parse items array or error message.
• example success response for list: {items: [{id: 154, name: "my-experiment", totalCost: 1200.50, monthCost: 150.25, userCount: 3, projectRole: 1, ...}]}.
• example success response for member add: {success: true} or empty object {}.

file location/persistence:

• no files are created or modified by this skill; all state is stored in bohrium backend at open.bohrium.com.
• bohr CLI maintains local cache of projects, but cache is refreshed on each command.

outcome signal

user knows operation succeeded when:

• list projects: CLI prints table/JSON/CSV showing all user's projects with correct names and IDs. if no projects exist, output is empty table or empty items array.

• create project: CLI prints success message with new projectId. newly created project appears in subsequent bohr project list output. project can be accessed at open.bohrium.com dashboard.

• delete project: CLI prompts for confirmation, then prints "project deleted" or similar. project no longer appears in project list. if user attempts to access deleted project via API, request returns 404.

• rename project: API returns HTTP 200. project name is updated in project list (run bohr project list --json to verify new name).

• add member: API returns HTTP 200. new member appears in GET /{projectId}/users response. new member can log in to bohrium and see project in their project list.

• remove member: API returns HTTP 200. removed member no longer appears in GET /{projectId}/users response. if member tries to access project, they receive access denied error.

• promote/demote admin: API returns HTTP 200. member's projectRole field in GET /{projectId}/users changes from 3 (member) to 1 (admin) or vice versa. admin gains or loses ability to add/remove members.

• set cost limit: API returns HTTP 200. subsequent attempts by members to submit jobs or start nodes when project cost exceeds limit will be rejected with "budget exceeded" error.

• recover deleted member: API returns HTTP 200. deleted member reappears in GET /{projectId}/users and can access project resources again.

edge case signals:

• if API returns 404 for a request: projectId does not exist, or v1 accessKey is not registered for that endpoint (see unavailable endpoints section).

• if API returns 401/403: accessKey is missing, invalid, or lacks permissions for the operation.

• if member add has no effect but API returns 200: target email does not exist; verify by calling GET /{projectId}/users and confirm email is missing.

• if project list is very long and newly created project is not visible: scroll to end of list; newly created project is appended to end.

• if delete project fails: user is not the creator, or project has unfinished jobs (unconfirmed; contact bohrium support if blocking issue occurs).

---

reference: roles and permissions

role	can create	can delete	can rename	can manage members	can adjust budget	can manage nodes/jobs/images
creator	n/a	yes	yes	yes	yes	yes
admin	no	no	no	yes	yes	yes
member	no	no	no	no	no	no

costs incurred by members are charged to the project creator's account balance, not member accounts.

---

reference: quotas and limits

resource	limit
self-created projects per user	4
nodes per user per project	4
concurrent running jobs per user	100
custom images per project	10
project shared disk (/share)	1TB free; additional capacity purchasable
personal data disk (/personal) per user per project	500GB free; additional capacity purchasable

contact bohrium support to increase quotas.

---

reference: billing

item	pricing model
compute resources	billed by duration; prices vary by node configuration (CPU, memory, GPU)
dev nodes	billed continuously while running; stop or delete when not in use
personal storage (/personal)	500GB free per user per project; overage charged per GB per month
project shared storage (/share)	1TB free per project; overage charged per GB per month

account balance is deducted every 5 minutes. warning email sent when balance drops below threshold (default ¥100). no new jobs can be submitted when balance reaches zero.

---

reference: shared resources

shared disk (/share):

• 1TB free per project, read/write access for all members.
• data persists after node release.
• access via web shell at open.bohrium.com or file management page.

shared images:

• all project members can see custom images created by other members in the bohrium image center.
• simplifies sharing of development environments and dependencies across team.

---

reference: unavailable API endpoints

the following endpoints return 404 or are otherwise inaccessible via openapi accessKey (v1):

endpoint	reason
POST /project/join	route forwarding path mismatch
POST /project/share_status	route forwarding path mismatch
GET /project/available	registered in accessKey v2 group only; unreachable via v1 accessKey

---

troubleshooting

problem	likely cause	solution
bohr CLI command not found	bohr CLI not installed or PATH not updated	run installation script (macOS or Linux) and source ~/.bashrc or ~/.zshrc
can't find newly created project in list	new project appended to end of list	run bohr project list --json and search for project name, or scroll to end of table output
API returns 401 or 403	accessKey missing, invalid, or not in request headers	verify ACCESS_KEY env var is set; obtain new key from open.bohrium.com account settings if needed
API returns 404	projectId doesn't exist, or endpoint is unsupported by accessKey v1	confirm projectId is numeric and exists; check unavailable endpoints table
adding member has no effect but API returns 200	target email not registered on bohrium	verify email is correct and registered on open.bohrium.com; call GET /{projectId}/users to confirm member was not added
can't remove member	wrong userId, or user is not creator/admin	get correct userId via GET /{projectId}/users; confirm your role is creator or admin
project deletion failed	user is not creator	only creators can delete projects; admins and members cannot
member can't submit jobs	project or member budget exceeded, or insufficient account balance	creator/admin adjusts budget via POST /set_cost_limit; creator tops up account balance at open.bohrium.com
can't promote/demote admin	user is not creator	only creators can manage admin roles; admins cannot promote/demote other admins
project count limit reached (max 4)	user has already self-created 4 projects	delete unused projects or contact bohrium support to request quota increase
API calls timeout or fail intermittently	network issue or bohrium service overload	retry with exponential backoff (1s, 2s, 4s); check bohrium status page

---

source: clawhub (bohrium project management documentation)