← ClaudeAtlas

meeting-scribelisted

Turn meeting audio into three artifacts -- a corrected transcript, an HTML visual canvas, and a Markdown summary with AI insights -- transcribing locally and cross-platform with Whisper (no cloud, no external transcription app). Runs on Apple Silicon mac via whisperkit-cli, on Intel mac / Windows / Linux via faster-whisper, or via whisper.cpp. MUST trigger when the user mentions a meeting transcript or recording, the audio drop-zone folder, processing / correcting / cleaning / fixing a transcript, transcribing an audio file, Whisper output, or generating meeting notes from a recording. Also trigger on Chinese phrasings -- 处理 transcript, 整理会议纪要, 修正 transcript, 清理 transcript, 修订 transcript, 转录纠错, 会议转写, 帮我做个会议总结, 把会议 transcript 处理一下, 处理一下昨天会议, 整理今天会议, 会议纪要, 转写文本, 把录音转成文字, 处理这个录音, 处理这个音频. Also trigger when the user drops an audio file (.wav / .mp3 / .m4a / .flac / .ogg ...) or a .txt transcript into the configured drop-zone folder. Behavior is driven entirely by a per-user config at ~/.config/meeting-transcripts/
breakthrough-edu/meeting-scribe · ★ 0 · Data & Documents · score 72
Install: claude install-skill breakthrough-edu/meeting-scribe
# Meeting Scribe -- Transcribe, Correct, Canvas, Summarize ## What this skill does Take a meeting **audio file** (or an already-transcribed `.txt`) that the user drops into the configured drop-zone, and produce three artifacts: 1. A **corrected transcript** (light-touch cleanup, speech features preserved) 2. A **visual canvas** (single self-contained HTML, the whole meeting at a glance) 3. A **summary** (Markdown, with an AI-insights section) Transcription runs **locally** via Whisper (no external app). The artifacts are written **directly to the configured output destination** -- never echoed in full to chat (echoing then writing generates the same content twice as output tokens and bloats context). The user reviews at the destination and requests edits there. All machine-specific behavior -- where audio lands, which Whisper model to use, where artifacts go, what language to write in -- comes from a per-user config file, NOT from this document. This skill is the orchestration logic only; it is portable across users and machines. ## Configuration On load (when the user invokes this skill), **read the config first**: ```bash cat ~/.config/meeting-transcripts/config.json ``` - **If it exists** -> parse it and use its values for every path / model / language decision below. Do not narrate this read. - **If it is absent** -> run **First-run setup** (below) once, write the config, then continue. ### Config schema ```json { "engine": "faster-whisper", "model": "large