Skip to content
UsecaseBoard
← All use cases
hackernewsOffice work

Make meeting transcripts searchable and improve a correction glossary

At a glance

A worker used Claude to clean transcripts, track commitments and build a searchable meeting archive. This workflow is listed under Office work, Meetings, Documents.

Agents / tools
Claude, Todoist, Obsidian

SourceBuilding a tool for these workflows? See weekly rates.

What they did

1) Transcribe meetings with Krisp and maintain a context document with a people directory, terminology glossary and a table of recurring speech-recognition mistakes. 2) Give each transcript and the context document to Claude. Have it reconcile names and terms against the error table, ask about genuinely unresolved items and wait for your answers. 3) After confirming the ambiguities, have it produce a Markdown summary with an overview, topic notes, decisions and action items; send the work items to Todoist and save the summary to Obsidian with YAML frontmatter and Dataview queries. 4) Add every confirmed correction back to the context document so the next transcript benefits, and query the accumulated notes across meetings.

How it went

The author says the evolving error table makes later summaries tighter and reduces the need for intervention.

Worth knowing

The author describes a custom pipeline; access to the transcript, notes and task system is needed, and connector configuration is not specified.

Save ideas in this browser. Upvotes count across the board.

Prompt excerpt

No prompt excerpt was provided by the source.

Sponsored

CodeBuddy

Tencent Cloud AI coding assistant for IDE and CLI.

Try CodeBuddy ↗
Explore all →