Breakthrough Meeting Scribe: Transcribe, Correct, Canvas, Summarize

What this skill does

Take a meeting audio file (or an already-transcribed .txt), either dropped into the configured drop-zone or pulled from a connected PLAUD recorder account, 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 always runs locally via Whisper (no external app), including for Plaud-sourced audio: Plaud is only a way for the audio to arrive, never a transcription backend, so a cloud provider's transcript quality and language handling never enter the pipeline. 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.

Two modes. The pipeline above (Phases 0-6) is the default, one meeting in, three artifacts out. A second entry point, Insights mode (see its section after Phase 6), runs when the user asks about their communication patterns ACROSS meetings: it reads the corpus of already-corrected transcripts and writes one analysis report. Route by intent: "process this recording" -> pipeline; "what are my patterns in meetings" -> Insights mode. Never run both in one pass.

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: