---
name: questlog
description: Query and manage the user's QuestLog voice recordings — transcripts, summaries, highlights, notes, stories, and speakers — through the QuestLog MCP connector. Use whenever the user asks about their recordings, interviews, meetings, oral histories, or notes captured in QuestLog.
---

# QuestLog

QuestLog turns the user's voice recordings (meetings, interviews, oral histories) into transcripts,
summaries, highlights, action items, detailed notes, and extracted stories — with speaker diarization
and naming. This skill helps you answer questions and make safe edits via the QuestLog MCP tools.

## Finding a recording
Recordings are referenced by **id or title** — titles are fuzzy-matched, so pass the user's phrasing
directly as the `recording` argument and the tools will resolve it.
- `list_recordings` — recent recordings (id, title, duration, speaker count). Start here for "what do I have?"
- `search_recordings` — keyword search across titles and content (word-boundary; "war" won't match "forward").
- If a title is ambiguous or returns several matches, list/search first and confirm with the user before acting.

## Reading
- `get_summary` — summary, highlights, action items. For a **merged recording** (several sessions stitched
  into one "master"), this automatically returns the whole-file *macro* summary, not one part's.
- `get_transcript` — full transcript with **speaker names**. Long transcripts are truncated to `maxChars`
  (default 100k); raise it for more, or read the summary/stories instead of the raw transcript when you can.
- `get_stories` — the distinct stories/anecdotes, each with who told it.
- `get_notes` — the AI's detailed notes plus the user's own added notes.

## Editing (all safe — nothing is ever deleted or overwritten)
- `append_note` — add a note to a recording (additive).
- `set_speaker_name` — name a speaker. Accepts a label (`SPEAKER_00`), a positional name ("Speaker 1"),
  or the speaker's current name. It locks the name so future AI guesses won't override it.
- `rename_recording` — change the title.
- `reevaluate` — rebuild the summary/notes from the latest transcript + the user's notes. **Asynchronous**
  (runs on QuestLog's GPU worker, takes from seconds to a few minutes). Use after adding notes or renaming speakers.
- `regenerate_stories` — re-extract the stories. **Asynchronous.**

## Good habits
- **Confirm before data-changing edits** (rename, set_speaker_name) — echo back what you'll change.
- After `set_speaker_name` or `append_note`, offer to `reevaluate` so the summary reflects the change.
- `reevaluate` / `regenerate_stories` are queued — tell the user it's processing and they can re-ask shortly.
- **Across many recordings**: `list_recordings` (or `search_recordings`) → `get_summary` for each → synthesize.
- This is the user's private data — only their own recordings are accessible, and only to them.

## Helping a stuck user
If the tools return nothing or error, help the user rather than just failing:
- **Empty `list_recordings`** → they're probably signed into the connector on a *different account* than the one holding their recordings. Have them remove and re-add the connector, signing in with the **same account and method** they use for QuestLog. The connector offers Google, Apple, and email sign-in.
- **A specific recording isn't found** → it may still be transcribing (only *done* recordings are listed) or the title is slightly off; try `search_recordings`, or ask them to confirm the exact title.
- **Auth or permission errors** → suggest removing and re-adding the connector in Claude → **Settings → Connectors** (URL `https://mcp.npcquestlog.com/mcp`), and allowing pop-ups during sign-in.
- Reassure them the connector is **read + safe additive edits only** — it never deletes and only sees their own data.
