Install
$ agentstack add skill-undefined-ui-second-brain-os-second-brain-transcript ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Clean a transcript
Concept pages built from unpunctuated caption dumps are noticeably worse, because the model spends its attention reconstructing sentence boundaries instead of understanding claims.
Core rule
Clean, never summarise. Nothing is cut. This is a formatting pass on the record, and the record has to stay faithful.
Workflow
- Punctuate and paragraph. Sentence boundaries first, then paragraphs at
topic shifts.
- Label speakers where they change. In an interview this is most of the
value.
- Fix technical terms. Auto-captions mangle proper nouns and jargon
consistently. Flag anything you could not resolve rather than guessing.
- Keep coarse timestamps every few minutes, so a claim on a wiki page can
be verified in ten seconds instead of a rewatch.
- Propose split points if the recording covers separate topics. A
three-hour podcast is not one source.
- Write frontmatter: title, channel or speaker, URL, date.
Output format
The cleaned transcript, then:
Cleaned:
Speakers labelled:
Terms corrected:
Uncertain:
Suggested splits:
Calibration
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: undefined-ui
- Source: undefined-ui/second-brain-os
- License: MIT
- Homepage: https://x.com/undefinedKi/status/2068306794116501544
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.