>- fix mistranscribed technical terms, and split long recordings by topic. Use this skill when the user drops an auto-generated transcript, subtitle file, podcast or lecture transcript, meeting recording text, or asks to process a video or audio source. Do NOT use for text that is already prose, for summarising a transcript, or for the ingestion itself.
npx skills add https://github.com/undefined-ui/second-brain-os --skill second-brain-transcript
Concept pages built from unpunctuated caption dumps are noticeably worse,
because the model spends its attention reconstructing sentence boundaries
instead of understanding claims.
Clean, never summarise. Nothing is cut. This is a formatting pass on the record,
and the record has to stay faithful.
topic shifts.
value.
consistently. Flag anything you could not resolve rather than guessing.
be verified in ten seconds instead of a rewatch.
three-hour podcast is not one source.
The cleaned transcript, then:
Cleaned: <source>
Speakers labelled: <n>
Terms corrected: <list>
Uncertain: <list of what could not be resolved>
Suggested splits: <topics with timestamps, or none>
Never drop filler that carries meaning, such as hedging or a speaker correcting
themselves. Those are exactly what distinguish a claim from an aside.
If the transcript is too garbled to clean reliably, say so and recommend
re-pulling it rather than producing a plausible reconstruction.
Take undefined-ui/second-brain-transcript from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.