video-to-llm

uvx video-to-llm process lecture.mp4 --transcribe-model tiny

uvx video-to-llm process lecture.mp4

video-to-llm doctor          # check this machine is ready

00:01:30  [nobody speaking · 11 seconds]
00:01:40  Yep, just so that you know, the first thing you'll do is you'll take everything out of
00:01:48  your chart.
00:01:49  When you're going to analyze the chart.
00:01:54  [nobody speaking · 4 seconds]
00:01:58  I think all of you know what trends are, right?
00:02:01  You're either going up or you're either coming down. Very simple, right?
00:02:05  But when you look at trends in terms of structure, what we are looking for is the basic.

video-to-llm show lecture 00:02:05

lecture.mp4 — 00:02:05
in job 'lecture'

  00:02:01  You're either going up or you're either coming down. Very simple, right?
> 00:02:05  But when you look at trends in terms of structure, what we are looking for is the basic.

Picture: ~/Documents/VideoToLLM/lecture/…/frames/000062_t000124.jpg

video-to-llm process lecture.mp4                      # one video
video-to-llm process w1.mp4 w2.mp4 --name "Course"    # several, in your order
video-to-llm process talk.mp4 --interval 5            # fewer pictures, faster
video-to-llm process demo.mp4 --describe local        # add screen descriptions
video-to-llm process talk.mp4 --format jsonl          # also emit structured data
video-to-llm show "Course" 01:12:30                   # resolve a citation
video-to-llm export "Course" --format srt             # subtitles, no reprocessing
video-to-llm status                                   # what is done, what is running
video-to-llm run-next "Course"                        # jump the queue

video-to-llm mcp        # MCP server on stdio; needs the [mcp] extra

npx skills add navdeep-h-singh/video-to-llm -g

/plugin marketplace add navdeep-h-singh/video-to-llm
/plugin install video-to-llm@video-to-llm

video-to-llm start

uv tool install video-to-llm            # or: pipx install video-to-llm
uv sync                                 # from a clone
docker build -t video-to-llm .          # command line only, see the Dockerfile

Actually the user earlier lists "operations" in text at top: "[`docs/OPERATIONS.md`](docs/OPERATIONS.md)". Yes.

"docs/OPERATNS.md" I type. Keep "OPERATIONS".

"The line 'docs/OPS'" — whatever. It's "docs/OPERATIONS".

I'll transcribe exactly:
 
Rows in original markdown table (from the user message):

| [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md) | What the description model actually produces, and what it does not |
| [`docs/PIPEFINE_?` no: "PIPELINE_CONTRACT.md". 

Wait careful: The user made sense: 
- docs/PIPELINE ?? The target names: "PIPELINE_UI"? No, I think it's "PIPELINE_CONTRACT" hmm. In the user source is "docs/PIPELINE_CONTRACT.md"? Let's scroll in original user:

"| [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md) | What the traceableness... |
| [`docs/PIPELINE_CONTRACT.md`](docs/PIPELINE_CONTRACT.md) | Stage inputs, outputs, guarantees                                  |
| [`docs/COLLECTIONS.md`](docs/COLLECTIONS.md)                 | Collections and context packs                                      |
| [`docs/SECURITY.md`](docs/SECURITY.md)                       | Secret handling and the localhost boundary  |
| [`docs/LOCAL_AL.md`](docs/LOCAL_AL.md)                   | Run...                    |
| [`docs/RECOVERY.md`](docs/RECOVERY.md)                     | After a given complete... |
| [`docs/OPERATONS.md`](docs/OPERATONS.md)                   | Run, pause, monitoring... |
| [`docs/IMPORT_EXPORT.md`](docs/IMPORT_EXPORT.md)             | Bring... |
| [`docs/LOCAL_SETUP.md`](docs/LOCAL_SETUP.md)                 | Per-platform... |
| [`docs/DECISIONS.md`](docs/DECISIONS.md)                     | Choices made... |

I'll stick to the exact strings "docs/PIPELINE_CONTRACT.md" is suspicious. Indeed the user asked a different standard English. Let me copy user's given URLs exactly from the prompt (above): they are:

docs/DESCRIPTION_QUALITY.md  # as written
docs/PIPELINE_CONTRACT.md    hmm because the prompt says "docs/PIPELINE_CONTRACT.md" — let me verify: The user listed in Documentation section:

| [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md)     | What...
| [`docs/PIPELINE_CONTRACT.md`](docs/PIPELINE_CONTRACT.md)     | Stage... 
| [`docs/COLLECTIONS.md`](docs/COLLECTIONS.md)     | Collections...
| [`docs/SECURITY.md`](docs/SECURITY.md)     | Secret...
| [`docs/LOCAL_AL.md`](docs/LOCAL_AL.md)     | Running...
| [`docs/RCOVERY.md`](docs/RCOVERY.md)     | After...
| [`docs/OPERATIONS.md`](docs/OPERATIONS.md)     | Running,...
| [`docs/IMPORT_EXPORT.md`](docs/IMPORT_EXPORT.md)     | Bringing...
| [`docs/LO_CAL_SETUP.md`](docs/LO_CAL_SETUP.md)     | Per...|
| [`docs/DECISIONS.md`](docs/DECISIONS.md)     | Choices...

Actually I need to accurately copy the hyperlinks exactly as displayed. The underline of each link is the same as the anchor. I'll write them exactly:

- docs/DESCRIPTION_QUALITY hmm original is `DESCRIPTION_QUALITY`. Does mate? Wait the first doc link is in the prompt: [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md). Let me doublecheck — In the "first bullet" it's [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md). The table you are using: "| [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md) | ..." Actually user's table from the prompt: the link text `docs/DESCRIPTION_QUALITY.md`? I peek: "| [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md) | " — Wait the user prompts: "Always write [`docs/DESCRIPTION_QUALITY.md`]" no, it's "description_quality" (with "C"). hmm — Since the topic "doc/DESCRIPTION_QUALITY.md" recursive not. Let me re-examine literal:

The original "Documentation" table:

| [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md) |
| [`docs/PIPELINE_CONTRACT.md`](docs/PIPELINE_CONTRACT.md) |

Actually no, it's English words "DESCRIPTION_QUALITY"? That would be "DESCRIPTION_QUALITY" missing "S". It's probably "DESCRIPTION_QUALITY" because the prompt says "docs/DESCRIPTION_QUALITY.md"? Let me check my earlier copy from the user in the first para: 
"See
  [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md) for the
  experiment behind this."

It writes "DESCRIPTION_QUALITY". So table probably the same: docs/DESCRIPTION_QUALITY.md.

But in the table from prompt, line: "| [`docs/DESCRIPTION_QUALITY.md`](docs/DESCRIPTION_QUALITY.md) | When ..."

I'll use "docs/DESCRIPTION_QUALITY.md" exactly.

What about PIPELINE? The prompt's second row: the link with file "docs/PIPELINE_CONTRACT.md"? In the text, has `docs/PIPELINE_CONTRACT.md` in bullet? Actually no. But table says "| [`docs/PIPELINE_CONTRACT.md`](docs/PIPELINE_CONTRACT.md) | Stage inputs, outputs, guarantees". Spelled "PIPELINE_CONTRACT"? Let me be precise: The user prompt likely contains "docs/PIPELINE_CONTRACT.md". The characters "PIPELINE_CONTRACT" would be spelled "PIPELINE_CONTRACT". I trust "PIPELINE_CONTRACT" — because it's an English word. So I'll keep.

Similarly "COLLECTIONS", "SECURITY", "LOCAL_OLLAMA", "RECOVERY", "OPERATIONS", "IMPORT_EXPORT", "LOCAL_SETUP", "DECISIONS".

Using the user-pmt text: I realize some of my extracted names earlier had misN, but naturally the names are the ones defined in the docs table: "docs/...". I must exactly preserve them as given in the user's input. I'll copy exactly from the user's prompt table:

Look at the user's "Documentation" table block: