Skip to content

Turn a long livestream transcript into one ordered learning page with the corrected key points

Exact prompt

# Turn a long livestream transcript into one ordered learning page Input: `transcript.txt`, a synthetic transcript of a pottery livestream. Each line is `[time] SPEAKER: text`; time is `m:ss` or `mm:ss` in the first hour and `h:mm:ss` after. HOST is the presenter; `chat @name` lines are viewers. Rules: - A topic is introduced by a HOST line "Let's talk about <Topic>."; its start is the first such line, written hh:mm:ss. - A key point is a HOST line "Key point on <Topic>: <name> is <value>." (value is the text up to the final full stop). Later HOST corrections replace the value: "Correction: <name> is <new>, not <old>." or "Correction on <name>: it's <new>." - Ignore viewer chat lines, and everything from a HOST line starting "Quick word from our sponsor" through the next HOST line "Okay, back to it." (that line included). - Order: a HOST line "Before <B>, you need <A>." means A comes before B. Put topics in an order that respects every such line; when several topics could come next, take the one that started earliest. - Write `out/learning.json`: `{"order": [<topic>, ...], "starts": {"<topic>": "hh:mm:ss", ...}, "points": {"<topic>": {"<name>": "<value>", ...}, ...}}`. - Write `out/learning.md`: for each topic in order, a line `## <Topic> (hh:mm:ss)`, then one line `- <name>: <value>` per key point in the order the points were first stated. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.

Turn a synthetic two-hour pottery livestream transcript into one study page. Topics come up out of teaching order and are revisited, prerequisites are stated in passing and must decide the order, the host corrects earlier key points in two different phrasings, viewers post wrong values in the same format, a sponsor segment plants a fake key point, and timestamps switch from m:ss to h:mm:ss after the first hour. Original benchmark task written for usecaserank.com (not based on a specific public post). Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked).

Success criteria: order starts corrections points_clean page

Best model for this task so far: Claude Haiku 5.5 (effort default (no --effort flag) · thinking on) (success, $0.0056, 21s).

Run this on another model

All runs (3)

100% pass rate across 3 eligible runs: 3 pass, 0 partial, 0 fail. Partial and failed runs are listed below with everything else.ⓘ

Runs for this use case
ModelCostTimeStep-insⓘAutonomyOutcomeTrustⓘDateCompare
AClaude Opus 5.5default · thinking on$0.1421s0Fully autonomouspassTrust 80%2026-10-23
AClaude Haiku 5.5default · thinking on$0.005621s0Fully autonomouspassTrust 80%2026-10-23
AClaude Sonnet 5.5default · thinking on$0.0621s0Fully autonomouspassTrust 80%2026-10-23

Embed this result

A live badge for this use case. It links back here and updates as new runs are published.

UseCaseRank badge for Turn a long livestream transcript into one ordered learning page with the corrected key points

Get new runs and ranking changes weekly

Which models got better or cheaper on real tasks like this one.