video-pipeline
Skill1 starsChanged 9 months agoMITView on GitHub
视频内容全链路处理。一个视频进去,文字稿+观点摘要+短视频切片+可发布文章全出来。串联 video-to-text → insight-extractor → video-clipper → article-forge 四个 skill 的完整流水线。适用于:直播回放、播客、会议录像的一站式内容加工。
6 other projects use a version of this.
Adopted by
Most recently taken up by
- notivn/AIEVv2their own version, first seen Nov 8, 2026
- kingbootoshi/video-alchemytheir own version, first seen Oct 25, 2026
- 439436269-ctrl/video-pipeline-skillstheir own version, first seen Oct 15, 2026
- notivn/AIEVtheir own version, first seen Oct 9, 2026
- Prawal-Bhuyan/claude-skillstheir own version, first seen Oct 8, 2026
- pjh2443391725-crypto/claude-skilltheir own version, first seen Jul 16, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- notivn/AIEVv2★ 136same name
- notivn/AIEV★ 132same name
- kingbootoshi/video-alchemy★ 9same name
- 439436269-ctrl/video-pipeline-skills★ 1same name
- pjh2443391725-crypto/claude-skill★ 0same name
- Prawal-Bhuyan/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- article-forgeSkill
- insight-extractorSkill
- video-clipperSkill
- video-to-textSkill
The file
Files
Video Pipeline — 视频内容全链路
一句话
丢一个视频进来,出一套完整的内容产品:文字稿 + 观点摘要 + 短视频切片 + 可发布文章。
链路总览
输入: 视频文件 (直播回放/播客/会议录像)
│
▼
┌─────────────────────────────────────────────┐
│ Stage 1: video-to-text │
│ 转写 → 带时间戳的文字稿 + JSON │
│ (去口吃的基础数据也在这里产生) │
└──────────────────┬──────────────────────────┘
│
┌──────────┴──────────┐
▼ ▼
┌───────────────┐ ┌─────────────────────┐
│ Stage 2: │ │ Stage 3: │
│ insight- │ │ video-clipper │
│ extractor │ │ 按观点切片 → │
│ 提炼观点/金句 │ │ 去静音/去口吃 → │
│ /争议点 │ │ 短视频成品 │
└───────┬───────┘ └─────────────────────┘
│
▼
┌───────────────────────────────────────────┐
│ Stage 4: article-forge │
│ 观点摘要 + 原始文稿 → 可发布文章 │
│ (博客/知乎/公众号) │
└───────────────────────────────────────────┘
输出目录: workspace/pipeline/<project-name>/
├── transcript.txt # 完整文字稿
├── transcript.json # 带时间戳 JSON
├── insights.md # 观点摘要
├── clips/ # 短视频切片
│ ├── 01-xxx.mp4
│ ├── 02-xxx.mp4
│ └── ...
└── articles/ # 生成的文章
├── blog-xxx.md
└── zhihu-xxx.md执行流程
输入参数
用户给出:
- 视频文件路径(必须)
- 项目名(可选,默认从文件名生成)
- 目标产出(可选,默认全部):
transcript— 只要文字稿insights— 文字稿 + 观点clips— 文字稿 + 切片articles— 文字稿 + 观点 + 文章all— 全部(默认)
- 文章平台(可选):blog / zhihu / wechat
- 切片数量(可选,默认 5-8 条)
Stage 1: 转写(video-to-text)
- 读取
video-to-textSKILL.md - 创建项目目录:
workspace/pipeline/<project-name>/ - 用 nohup 后台执行转写脚本:
nohup python3 {video-to-text-skillDir}/scripts/transcribe.py \ /path/to/video.mp4 \ --output-dir workspace/pipeline/<project-name>/ \ --output-name transcript \ --diarize \ > /tmp/pipeline-transcribe.log 2>&1 & - 等待完成(用 process poll 或检查输出文件)
- 产出:
transcript.txt+transcript.json
⚠️ 这是最耗时的阶段,30 分钟视频大约需要 10-20 分钟转写。后续阶段都很快。
Stage 2: 观点提炼(insight-extractor)
- 读取
insight-extractorSKILL.md - 输入
transcript.txt - 按 insight-extractor 流程提炼:
- 话题边界识别
- 核心论点提取
- 金句标注(保留时间戳)
- 争议点标注
- 产出:
insights.md
关键: 金句和观点的时间戳要精确,Stage 3 切片需要用。
Stage 3: 视频切片(video-clipper)
可以和 Stage 2 并行(都只依赖 Stage 1 的输出)。
- 读取
video-clipperSKILL.md - 基于
insights.md的观点 +transcript.json的时间戳定位切片边界 - 执行四阶段切片流程:
- 用
batch-clip-v4.sh批量切片(去静音 + 去口吃 + crossfade) - 用
batch-postcheck.sh二次质检 - 必要时用
iterate-until-clean.py迭代修复
- 用
- 产出:
clips/01-xxx.mp4,clips/02-xxx.mp4, ...
优化: 优先切 insights 中标记为「金句」和「争议点」的片段——这些做短视频最有传播力。
Stage 4: 文章生成(article-forge)
- 读取
article-forgeSKILL.md - 输入
insights.md+transcript.txt - 根据目标平台选择文体和风格
- 生成文章,严格执行去 AI 味
- 产出:
articles/blog-xxx.md或articles/zhihu-xxx.md
可选: 如果用户要求发布,调用 ZhiForge 的发布流程。
并行策略
时间线:
─────────────────────────────────────────────────>
Stage 1 (转写) Stage 2 (观点) Stage 4 (文章)
████████████████ ████████ ████████
Stage 3 (切片)
████████████████- Stage 2 和 Stage 3 可以并行(用 sessions_spawn 分别跑)
- Stage 4 依赖 Stage 2 的输出,串行
- Stage 1 最慢,占总时间 60-70%
子 agent 编排
推荐用 sessions_spawn 并行化:
主 agent:
1. 启动 Stage 1(转写,等待完成)
2. spawn 子 agent A → Stage 2(观点提炼)
3. spawn 子 agent B → Stage 3(视频切片)
4. 等 A 完成 → 启动 Stage 4(文章生成)
5. 等 B 完成 → 汇总输出输出汇总模板
全部完成后,向用户汇报:
🎬 视频内容处理完成
📹 源文件:xxx.mp4 (时长 XX:XX)
📁 项目目录:workspace/pipeline/<name>/
📝 文字稿:transcript.txt (XXXX 字)
💡 观点提炼:insights.md
- X 个核心观点
- X 条金句
- X 个争议点
🎞️ 短视频切片:X 条
- 01-xxx.mp4 (XX:XX) — 主题
- 02-xxx.mp4 (XX:XX) — 主题
- ...
📄 文章:X 篇
- blog-xxx.md (XXXX 字) — 标题
- zhihu-xxx.md (XXXX 字) — 标题快速触发
用户说以下任何一种,触发此 skill:
- "处理这个视频"
- "视频全链路"
- "直播回放处理"
- "把这个视频变成内容"
- "video pipeline"
默认执行 all(全部产出),除非用户指定只要某个阶段。
注意事项
- Stage 1 转写必须用 nohup 后台,否则超时
- 文件名含中文要建英文 symlink
- 切片依赖 transcript.json 的 word_segments,不是 transcript.txt
- 文章生成依赖 insights.md,不能跳过 Stage 2 直接到 Stage 4
- 所有产出存
workspace/pipeline/<project-name>/,不用 /tmp/ - 用完浏览器后必须
browser stop
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

