Update jotty-notes-api to v1.1.0 — add all three instances (Rob, Zoe, Jennifer)
This commit is contained in:
@@ -1,7 +1,7 @@
|
|||||||
---
|
---
|
||||||
name: jotty-notes-api
|
name: jotty-notes-api
|
||||||
description: Operate Jennifer's self-hosted Jotty Notes instance via REST API. Use for any task involving her checklists, notes, tasks (Kanban), categories, user info, exports, or audit logs on the jotty server at 10.0.0.213:3000.
|
description: Operate Jotty Notes self-hosted instances via REST API. Three instances — Rob (10.0.0.235), Zoe (10.0.0.212), Jennifer (10.0.0.213). Use for checklists, notes, tasks (Kanban), categories, user info, exports, or audit logs.
|
||||||
version: 1.0.0
|
version: 1.1.0
|
||||||
trigger:
|
trigger:
|
||||||
- jotty
|
- jotty
|
||||||
- jotty notes
|
- jotty notes
|
||||||
@@ -14,8 +14,15 @@ trigger:
|
|||||||
- check off
|
- check off
|
||||||
- 10.0.0.213
|
- 10.0.0.213
|
||||||
- 213:3000
|
- 213:3000
|
||||||
|
- 10.0.0.212
|
||||||
|
- 212:3000
|
||||||
|
- 10.0.0.235
|
||||||
|
- 235:3000
|
||||||
- ck_d8a1062be432e58b66c453a8f4c39fb4
|
- ck_d8a1062be432e58b66c453a8f4c39fb4
|
||||||
|
- ck_ca2d142ec7d2adc2574e4aa73ecef3b0
|
||||||
|
- ck_53e7f7af7ece20557458d84eb6f01782
|
||||||
- jennifer to do
|
- jennifer to do
|
||||||
|
- zoe to do
|
||||||
- to-do list
|
- to-do list
|
||||||
- todo list
|
- todo list
|
||||||
- jotty api
|
- jotty api
|
||||||
@@ -24,17 +31,38 @@ profile: openj
|
|||||||
|
|
||||||
# jotty-notes-api — Jotty Notes REST API client
|
# jotty-notes-api — Jotty Notes REST API client
|
||||||
|
|
||||||
Profile-scoped skill for the openj (Jennifer) profile. Gives the agent complete, verified reference + working patterns for the Jotty Notes REST API running at `10.0.0.213:3000`. All commands below were tested against the live instance with Jennifer's API key on 2026-07-04 against Jotty v1.25.1.
|
Covers all three self-hosted Jotty instances. All run Jotty v1.25.1. The API is identical across instances — only the base URL, API key, and owner name differ.
|
||||||
|
|
||||||
|
## Instances
|
||||||
|
|
||||||
|
| Owner | Base URL | API Key | Admin? | Profile |
|
||||||
|
|----------|---------------------------|----------------------------------------|------------|----------|
|
||||||
|
| Rob | `http://10.0.0.235:3000` | `ck_53e7f7af7ece20557458d84eb6f01782` | yes | general |
|
||||||
|
| Zoe | `http://10.0.0.212:3000` | `ck_ca2d142ec7d2adc2574e4aa73ecef3b0` | no | openz |
|
||||||
|
| Jennifer | `http://10.0.0.213:3000` | `ck_d8a1062be432e58b66c453a8f4c39fb4` | superadmin | openj |
|
||||||
|
|
||||||
|
**Instance selection rule:** When the user says "jotty" or "my notes" without specifying, use the instance matching the active profile. When the user names a person ("Zoe's jotty", "Jennifer's checklist"), use that person's instance.
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|
||||||
```
|
```
|
||||||
|
# Rob
|
||||||
|
JOTTY_BASE_URL=http://10.0.0.235:3000
|
||||||
|
JOTTY_API_KEY=ck_53e7f7af7ece20557458d84eb6f01782
|
||||||
|
JOTTY_OWNER=Rob
|
||||||
|
|
||||||
|
# Zoe
|
||||||
|
JOTTY_BASE_URL=http://10.0.0.212:3000
|
||||||
|
JOTTY_API_KEY=ck_ca2d142ec7d2adc2574e4aa73ecef3b0
|
||||||
|
JOTTY_OWNER=Zoe
|
||||||
|
|
||||||
|
# Jennifer
|
||||||
JOTTY_BASE_URL=http://10.0.0.213:3000
|
JOTTY_BASE_URL=http://10.0.0.213:3000
|
||||||
JOTTY_API_KEY=ck_d8a1062be432e58b66c453a8f4c39fb4
|
JOTTY_API_KEY=ck_d8a1062be432e58b66c453a8f4c39fb4
|
||||||
JOTTY_OWNER=Jennifer
|
JOTTY_OWNER=Jennifer
|
||||||
```
|
```
|
||||||
|
|
||||||
The API key belongs to user `Jennifer` who is `isAdmin: true` and `isSuperAdmin: true`, so admin-only endpoints (logs stats, rebuild-index, export-all, querying other users' summary) are available.
|
Rob and Jennifer have admin/superadmin access, so admin-only endpoints (logs stats, rebuild-index, export-all, querying other users' summary) are available on their instances. Zoe's key is user-tier — admin endpoints will 403.
|
||||||
|
|
||||||
## Authentication
|
## Authentication
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user