A tutorial video can serve two different needs: help someone understand a procedure, or provide instructions an agent can reuse. In Qwen-MM-Plugins, that distinction is a useful starting point for choosing between omni-video2note and omni-skill-creator—before spending time on setup.
The Qwen-MM-Plugins README, captured on September 18, 2026, documents both capabilities. That is an observation date, not an established release date. This comparison is about their documented purposes, not tested output quality.
Choose the deliverable before the plugin
| Intended outcome | Documented capability | What the README actually says |
|---|---|---|
| An illustrated reference for a person learning or reviewing a procedure | omni-video2note |
Converts a local tutorial video into an illustrated PDF using Omni audio-video understanding, “with review feedback.” |
| A reusable instruction artifact for an agent | omni-skill-creator |
Turns a demonstration video into a reusable Agent Skill. |
My recommendation is to choose by who needs to use the result next. If a documentation owner needs a reference that people can inspect, the PDF capability matches that deliverable. If an automation lead wants to explore task reuse by an agent, the Skill capability matches that purpose—but the generated artifact still needs evaluation.
For example, imagine a recorded walkthrough of a routine internal procedure. “Give a colleague illustrated notes to check while following it” points toward omni-video2note. “Produce a Skill we can evaluate for repeating the demonstrated task” points toward omni-skill-creator. These are proposed selection criteria, not claims that either plugin will successfully handle that particular recording.
If both outcomes matter, treat them as two deliverables with separate acceptance checks. A readable PDF is not evidence that a generated Skill will execute correctly; a Skill artifact is not evidence that the procedure is clearly explained to a person.
Shared prerequisites are only the start
Both capability entries explicitly require a DashScope key and ffmpeg. The README also lists uv, which provides uvx, under general requirements, and points to the installation guide for exact versions and optional extras.
Do not read “DashScope key and ffmpeg” as a complete setup specification. Before choosing an adoption path, check the installation documentation for the intended environment. This comparison does not establish version requirements, costs, or portability of generated Skills across agent harnesses.
Decide who accepts the output
The PDF entry’s phrase “with review feedback” is narrower than a quality guarantee. The captured README does not specify who reviews it, which review stages occur, or whether feedback automatically corrects the result.
For a pilot, I would set these acceptance checks outside any presumed built-in review:
- PDF: Have a documentation owner compare the steps and illustrations with the source video. Flag missing prerequisites, ambiguous ordering, or an illustration that does not support the accompanying instruction before sharing it as a reference.
- Skill: Have an automation owner evaluate the generated artifact on a controlled task, with expected results and stop conditions defined in advance. Review what it proposes to do before permitting consequential actions. Creating the artifact is not the same as demonstrating successful execution.
These are recommendations, not completed tests or proof of safety. The README supports a deliverable-choice decision; it does not support an accuracy, speed, or reliability ranking between the two capabilities.
The practical question is therefore not “Which plugin is better?” It is “Do we need a reference a person can review, or a Skill we are prepared to test?” Name that consumer—and the person responsible for acceptance—before turning the video into either output.