meeting-transcriptionlisted

Operates and manages a context-aware meeting-transcription pipeline (2-track or single-mix recording → whisper.cpp large-v3 + pyannote diarization on a worker host → voice-matched speaker names → naked transcript delivered to /debrief; the summary is made later by the in-session /debrief, never by the worker). The reference implementation of the transcription-worker contract (docs/transcription-worker.md). Use this skill WHENEVER the user wants to transcribe a meeting, set up or change a transcription context/folder, add or re-train a speaker voice, reprocess a recording, extend the pipeline, or troubleshoot it — even if they don't name the pipeline explicitly. Triggers: "transcribe a meeting", "transcription folder", "new transcription context", "add a speaker", "train a voice", "voice library", "speaker recognition", "speaker diarization", "who said what", "reprocess recording", "transcribe pipeline", "update the whisper model". Also use it to answer "how does my transcription system work" — it is the sourc
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74

Install: claude install-skill bks-lab/open-bridge

# Meeting Transcription Pipeline A pipeline that turns meeting recordings into clean, structured Markdown transcripts with **named speakers**. It is **context-aware**: each context (e.g. `main`, `customer-x`) has its own voice library, language default, and output routing, so the same system serves internal standups and customer calls in different languages without reconfiguration. This skill is both the **knowledge base** (how the system works) and the **operations manual** (how to change it). The canonical scripts live in `scripts/` here and are deployed to the worker host's `~/transcribe-pipeline/`. It is the reference implementation of the bring-your-own-worker contract in [`docs/transcription-worker.md`](../../docs/transcription-worker.md) — `/debrief` talks to it only through `scripts/debrief_sync.sh` (`pull` / `push`). ## Configuration — the yaml wiring Three config surfaces, same pattern as every other capability: **1. `bridge-config.yaml` — the integration block** (is the capability on, which script, which contexts — registration + routing): ```yaml integrations: transcription: enabled: true sync_script: "skills/meeting-transcription/scripts/debrief_sync.sh" default_context: main # context for audio handed off without an explicit one contexts: main: # → workflow/contexts/main.yaml imports: work/imports # where this context's transcripts land on pull ``` `BRIDGE_IMPORTS` / `TRANSCRIBE_CONTEXTS` env-