Boya OS

View saved version →

---
name: boya-os-recordings
description: Use when the user wants to view their own Boya OS recordings, find a recording by something said in it, read a transcript, AI summary, mind map, or action items, or check their bound recording devices and folders. Trigger words: my recordings, recording list, what did I record, find a recording, search recordings, transcript, summary, meeting notes, mind map, action items, to-dos, devices, folders.
---

# Boya OS Recordings

Read-only access to the signed-in user's own recordings and derived content: transcripts, AI summaries, mind maps, action items, folders, and bound devices. This skill never records, edits, deletes, generates, or regenerates anything.

All data is scoped to the currently authorized Boya OS account. Never use it to look for another user's data.

## 1. Choose the right tool

| User intent | Tool |
|---|---|
| "What did I record this week / today?" | `list_recordings` |
| "I remember X was said in a recording" | `search_recordings` |
| "What folders do I have, and how many recordings?" | `list_folders` |
| "Which recording devices are bound?" | `list_devices` |
| "Show details / duration / transcription status" | `get_recording` |
| "Give me the transcript / full text" | `get_transcript` |
| "Give me the summary / meeting notes" | `get_summary` |
| "Show me the mind map" | `get_map` (mind map only) or `get_summary` (full summary) |
| "What are my action items / to-dos?" | `get_action_items` |

Browsing versus searching: use `list_recordings` to browse by date, folder, or duration; use `search_recordings` when the user remembers a keyword but not which recording it was.

## 2. Chain through `recording_id`

Every tool except `list_recordings`, `search_recordings`, `list_folders`, and `list_devices` requires a `recording_id`.

```
list_recordings / search_recordings
        -> take recordingId from each returned item
        -> pass it as recording_id to get_recording / get_transcript / get_summary / get_map / get_action_items
```

- `recordingId` is the stable recording/upload identifier. Never use a title as an ID; titles can repeat.
- Never invent a `recording_id`. If the user has not identified the recording, search or list first.

## 3. Page through all results

`list_recordings` and `search_recordings` return `total` (all matches) and the current page in `items`. If fewer items than `total` have been returned and the user needs a complete answer, increase `page` until all matches are read.

`page_size` is 1-100 (default 20). Do not conclude "that is everything" from the first page unless `items` covers `total`.

## 4. Check derived flags before calling downstream tools

`list_recordings` and `get_recording` return flags that tell you whether readable content exists:

| Flag | Meaning | Call only when true |
|---|---|---|
| `hasTranscript` | A readable transcript exists | `get_transcript` |
| `hasSummary` | An AI summary exists | `get_summary` |
| `hasMindmap` | A mind map exists | `get_map` |
| `hasActionItems` | On/off flag only; details are not included | Always call `get_action_items` for details |
| `status` | `pending` / `processing` / `success` / `failed` | Only `success` can have content |

This avoids ineffective calls when a recording is still processing or has no derived content.

## 5. Empty results are normal responses, not errors

| Situation | Response | How to reply |
|---|---|---|
| Not transcribed, or transcription failed | `get_transcript` returns `status != success` and empty content | "This recording does not have a transcript yet." |
| No summary, or summary generation failed | `get_summary` returns `hasSummary=false` and null content fields | "This recording does not have a summary yet." |
| No mind map | `get_map` returns `hasMap=false` and an empty string | "This recording does not have a mind map yet." |
| No action items | `get_action_items` returns `items: []`, `total: 0` | "There are no action items right now." |

If the user wants to ge

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.