monologue-notes-api — Claude Code skill: read notes via REST API
monologue-notes-api — a skill to read and search Monologue notes through the REST API. Handles auth via MONOLOGUE_API_KEY, supports pagination, time filters, and full-text search.
CC0-1.0 221 installs ★ 304 updated 2026-04-25
npx skills add intellectronica/agent-skills --skill monologue-notes-api -a claude-codeWhat monologue-notes-api does
This skill covers direct interaction with the Monologue Notes read-only REST API using curl or any HTTP client. Two key endpoints: GET /v1/public-api/notes lists notes with limit, cursor-based pagination, q for search, and filters for creation and update timestamps; GET /v1/public-api/notes/{note_id} retrieves full note details including transcript and transcript segments.
Auth uses the MONOLOGUE_API_KEY environment variable as a bearer token in the Authorization header. The skill covers safe token handling—checking presence without logging it, handling errors like 401 (invalid token), 403 (missing notes:read scope), and 404 (note not found). Responses are JSON with ISO 8601 timestamps; you can pipe to jq for custom output.
Search works across titles, summaries, and transcripts. For large result sets, cursor-based pagination fetches pages of 20–100 items; pass the next_cursor from one response back as the cursor parameter to the next request, stopping when next_cursor is absent. The skill blocks API calls if MONOLOGUE_API_KEY is missing and prompts the user to supply a token.
What it helps with
- search notes by keyword in title, summary or transcript
- fetch full text and structured segments from a single note
- page through large lists of notes, 20–100 per page
- filter notes by creation or modification date
- safely pass API credentials without exposing them in logs
Example prompts for the agent
- Find all notes containing the word “interview” in the content
- Get the full text of the note with ID
NOTE_ID - Show the 50 most recent notes created after 2026-01-01
How to install monologue-notes-api
1Skills CLI (Vercel)
npx skills add intellectronica/agent-skills --skill monologue-notes-api -a claude-code2Manually: put the files in place
~/.claude/skills/monologue-notes-api/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/monologue-notes-api/
1Skills CLI (Vercel)
npx skills add intellectronica/agent-skills --skill monologue-notes-api -a codex2Manually: put the files in place
.agents/skills/monologue-notes-api/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add intellectronica/agent-skills --skill monologue-notes-api -a cursor2Manually: put the files in place
.cursor/skills/monologue-notes-api/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install intellectronica/agent-skills skills/monologue-notes-api2Manually: put the files in place
.github/skills/monologue-notes-api/SKILL.md1Skills CLI (Vercel)
npx skills add intellectronica/agent-skills --skill monologue-notes-api -a gemini-cli2Platform CLI
gemini skills install https://github.com/intellectronica/agent-skills --path skills/monologue-notes-apiManually: put the files in place
.devin/skills/monologue-notes-api/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add intellectronica/agent-skills --skill monologue-notes-api -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about monologue-notes-api
How do I install monologue-notes-api in Claude Code?
Run npx skills add intellectronica/agent-skills --skill monologue-notes-api -a claude-code, then open ~/.claude/skills/monologue-notes-api/SKILL.md.
What does monologue-notes-api do?
The skill enables your agent to call the Monologue Notes REST API for read-only access. It handles authentication, pagination with cursors, time-based filters, and full-text search across note contents.
What do I need to use this skill?
Set the MONOLOGUE_API_KEY environment variable with a valid API token that has the notes:read scope. Without it, the skill will refuse to make requests and ask the user for a key.
Source text
SKILL.md · CC0-1.0
---
name: monologue-notes-api
description: >
Use this skill when the user wants to read or search their Monologue notes through the
Monologue Notes REST API. It covers authentication with the MONOLOGUE_API_KEY environment
variable, safe token handling, listing notes, fetching a single note, pagination, filters,
and error handling. The API is read-only and should be accessed with direct HTTP requests
such as curl or any equivalent REST client.
---
# Monologue Notes API
This skill provides the information needed to call the Monologue Notes REST API directly.
Use it for read-only operations on the authenticated user's notes.
Use whatever HTTP client fits the task: `curl`, a short script, or another REST-capable tool.
Do not invent client libraries unless the user asks for one.
## Authentication
Use the environment variable `MONOLOGUE_API_KEY` as the bearer token.
- Required auth header: `Authorization: Bearer $MONOLOGUE_API_KEY`
- Required scope: `notes:read`
- Never print the token, echo it, log it, or include it in a response to the user
- Only pass it through the `Authorization` header as a shell variable expansion
Check whether the token is available without displaying it:
```bash
if [ -z "${MONOLOGUE_API_KEY:-}" ]; then
echo "MONOLOGUE_API_KEY is not set"
fi
```
If `MONOLOGUE_API_KEY` is missing:
- Report that the environment variable is not present
- Ask the user whether they want to provide an API key
- Do not attempt authenticated API calls until a token is available
Avoid commands such as these because they would expose secrets:
```bash
echo "$MONOLOGUE_API_KEY"
env | grep MONOLOGUE_API_KEY
set | grep MONOLOGUE_API_KEY
```
## Base URL
- Base URL: `https://api.monologue.to`
- API shape: read-only Notes API
- Data format: JSON
- Timestamps: ISO 8601 date-time strings
## Request Pattern
For all requests:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/..."
```
If structured output is useful, pipe the response to `jq`.
## Endpoints
### List notes
`GET /v1/public-api/notes`
Returns a page of notes for the authenticated user.
Supported query parameters:
- `limit`: integer from `1` to `100`, default `20`
- `cursor`: opaque pagination cursor from a previous response
- `created_after`: ISO 8601 timestamp
- `created_before`: ISO 8601 timestamp
- `updated_after`: ISO 8601 timestamp
- `q`: full-text search across titles, summaries, and transcripts
Example:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/v1/public-api/notes?limit=20&q=interview"
```
Example with `jq`:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/v1/public-api/notes?limit=20" \
| jq '{next_cursor, items: [.items[] | {note_id, title, summary, created_at, updated_at}]}'
```
Expected response fields:
- `items`: array of note summaries
- `next_cursor`: cursor for the next page, if any
Each list item may include:
- `note_id`
- `title`
- `summary`
- `created_at`
- `updated_at`
Possible errors:
- `400`: invalid filter or cursor
- `401`: missing or invalid token
- `403`: token lacks the required scope
- `422`: validation error
### Get a single note
`GET /v1/public-api/notes/{note_id}`
Returns the full details for one note belonging to the authenticated user.
Path parameters:
- `note_id`: note identifier returned by the list endpoint
Example:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/v1/public-api/notes/NOTE_ID"
```
Example with `jq`:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/v1/public-api/notes/NOTE_ID" \
| jq '{note_id, title, summary, transcript, transcript_segments, created_at, updated_at}'
```
In addition to the list fields, the full note response may include:
- `transcript`
- `transcript_segments`
Notes:
- `transcript_segments` is loosely typed structured JSON and may be `null`
- `404` means the note was not found for the authenticated user
Possible errors:
- `401`: missing or invalid token
- `403`: token lacks the required scope
- `404`: note not found
- `422`: validation error
## Common Workflows
### Search notes by keyword
Use the `q` parameter:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/v1/public-api/notes?q=meeting"
```
Search covers:
- note titles
- note summaries
- note transcripts
### Page through results
1. Call `GET /v1/public-api/notes`
2. Read `next_cursor` from the response
3. Pass that cursor back as the `cursor` query parameter
4. Stop when `next_cursor` is absent or `null`
Example:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/v1/public-api/notes?limit=50&cursor=OPAQUE_CURSOR"
```
### Filter by time
Use ISO 8601 date-time values:
```bash
curl -sS \
-H "Authorization: Bearer $MONOLOGUE_API_KEY" \
"https://api.monologue.to/v1/public-api/notes?created_after=2026-01-01T00:00:00Z"
```
## Operating Rules
- Treat this API as read-only
- Do not claim write support; this skill only covers listing and reading notes
- Prefer `https://api.monologue.to` for requests
- When reporting failures, summarise the HTTP status and relevant response body without exposing the token
- If the user asks for a workflow that requires local post-processing, fetch the data first and then transform it separately
## Source Notes
This skill is based on:
- `/Users/eleanor/repos/obsidian/intellectronica/2026-04-21-20-10 Monologue API.md`
- Live OpenAPI checks against `https://api.monologue.to/public-openapi.json` on 2026-04-22
© intellectronica · CC0-1.0 · intellectronica/agent-skills