Component · for humans & their agents
Transcript-to-Chapters Pipeline
verified · first-partyactively maintained$0 during beta (was $59)
YouTube renders NO chapters if the first is not at 00:00, there are fewer than three, or any is under 10 seconds — with no error anywhere.
by Code Recycle
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 64 tests · 8/10 mutations caught
Turns a timestamped transcript into chapter markers that actually render.
Turns a timestamped transcript into chapter markers that actually render.
THE SILENT FAILURE. YouTube enforces its chapter rules by IGNORING your chapters, not by rejecting them. First chapter must start at 00:00, there must be at least three, each at least 10 seconds. Break any one and YouTube simply renders nothing — no error, no warning. The creator sees timestamps sitting in their description and assumes it worked. Naive splitters break all three constantly: they start at the first detected topic rather than zero, emit two chapters for a short video, and emit sub-10-second chapters around quick topic changes.
When the input CANNOT satisfy the rules — too short, too few topics — this REFUSES with a reason rather than emitting markers that will silently not render. Segments below the minimum are merged into their neighbour rather than dropped. Timestamps over an hour switch to HH:MM:SS correctly, which is a classic off-by-one that produces markers the platform ignores.
Title generation is caller-injected with a deterministic offline fallback, so tests need no API key.
VERIFIED: 64 tests, 10 deliberate defects applied to the real source, 8 caught and 2 proved to change no observable behaviour (a defensive assertion that only fires if the merge itself is buggy, and a guard the duration gate above it already makes unreachable) — the proofs ship in mutations.json. Every mutation was observed FAILING before the source was restored — a test never seen to fail is a decoration.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function buildChapters( segments: TranscriptSegment[], options: BuildChaptersOptions = {}, ): BuildChaptersResult;
export function toYouTubeDescription(chapters: Chapter[]): string;
export function formatTimestamp(totalSeconds: number): string;
export function validateSegments(segments: TranscriptSegment[]): void; export type TitleFn = (span: { start: number;
export type RefusalCode = "video_too_short" | "too_few_topics_after_merge";
export type BuildChaptersResult = | { ok: true;01Capabilities
Does
- + Creator operations
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 64/64 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 18 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 4, 2026 | First public release. |