Claude Code 技巧:用 Opus 5.5 生成视频前的自动化质检流程
Claude Code tip: before you post a video Opus 5.5 made to X, have it send out 𝟯…
提供了一套结构完整、可直接复用的 AI 视频自动化质检方案,包含具体的代理分工、检查清单和 Prompt 逻辑,对同类创作者极具实操参考价值。
Claude Code tip: before you post a video Opus 5.5 made to X, have it send out 𝟯 𝗿𝗲𝘃𝗶𝗲𝘄𝗲𝗿 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to flag problems by timestamp against 𝘁𝗵𝗲𝘀𝗲 𝟵 𝗰𝗵𝗲𝗰𝗸𝘀, and only bring it to you once all 3 score it 7 or higher.
Claude Code 技巧:在你将 Opus 5.5 制作的视频发布到 X 之前,让它派出 3 个评审子代理(reviewer subagents),根据以下 9 项检查标准按时间戳标记问题,只有当所有 3 个代理都给出 7 分或更高时,才将其呈现给你。
Both videos I made last week went through 3 reviewer subagents. One took 3 rounds, and its scores went from 𝟱/𝟲/𝟲 𝘁𝗼 𝟴/𝟴/𝟴.
我上周制作的两条视频都经过了 3 个评审子代理的审核。其中一条经历了 3 轮修改,其分数从 𝟱/𝟲/𝟲 提升到了 𝟴/𝟴/𝟴。
Opening → When X autoplays a video, frame 0 is the thumbnail. Does it open on a blank screen, a black frame or something still fading in? → Watch the first 3 seconds on mute. Can you tell what it's about?
开场 → 当 X 自动播放视频时,第 0 帧即为缩略图。它是从空白屏幕、黑屏还是逐渐显现的画面开始播放的? → 静音观看前 3 秒。你能看出它在讲什么吗?
Visuals → Only review frames pulled from the exported MP4. Something that looks fine in the preview can disappear in the render. → Record a demo that loops back and forth on a page, and half of what you capture plays in reverse. Does every clip you cut in play forward? → Is there a black frame or fade-out in the middle that makes people think it's over? → Does the last frame lead back into the first? X plays videos on a loop.
视觉效果 → 仅审查从导出的 MP4 中提取的帧。预览中看起来正常的画面在渲染后可能会消失。 → 录制一个在页面上来回循环演示的视频,你捕捉到的内容有一半是倒放的。你在剪辑中的每个片段是否都能正向播放? → 中间是否有黑屏或淡出效果,让人误以为视频已经结束? → 最后一帧是否能无缝衔接回第一帧?X 会循环播放视频。
Content → Does every caption and number match the source material? Does a claim like "the first" have a source? → Are captions or key info sitting in the bottom 8%? X's mobile player covers that strip. → Shrink it to phone width. Can you still read the text?
内容 → 每条字幕和数字是否与源材料一致?诸如“第一个”之类的说法是否有来源依据? → 字幕或关键信息是否位于底部 8% 的区域?X 的移动播放器会遮挡该区域。 → 缩小至手机宽度。你还能看清文字吗?
Run all 3 on Opus 5.5 at high effort. After each round of fixes, have the same subagent review the new version. It remembers what it flagged last round and checks those first.
以高努力模式对 Opus 5.5 运行这 3 个代理。每轮修复后,让同一个子代理审核新版本。它会记住上一轮标记的问题并优先检查这些内容。
If the main session takes more than 5 minutes to fix and re-render, the subagents' cache expires. When they pick up again, every image from earlier rounds gets processed from scratch, and that counts more against your usage limits. So the prompt gives each of them a 1-hour cache.
如果主会话花费超过 5 分钟进行修复和重新渲染,子代理的缓存就会过期。当它们再次启动时,早期轮次的所有图像都会从头处理,这会更多地消耗你的使用限额。因此,提示词为每个代理提供了 1 小时的缓存。
For the sound, follow the quoted post. It shows how to measure it.
关于声音部分,请遵循引用帖子的方法。它展示了如何测量音频质量。
Send this whole post to Claude Code, and add this line at the end 👇
将此完整帖子发送给 Claude Code,并在末尾添加这一行 👇
"Create 3 reviewer subagents in ~/.claude/agents, one for each group above: hook-reviewer, motion-reviewer and content-reviewer. Use model opus and effort high, and give them only Read, Glob and Grep. They review and never edit. In each one's frontmatter, write experimental: and put cacheTtl: 1h on the next line, indented. If my Claude Code is older than 2.1.248, or subagentPromptCacheTtl is set in my settings, tell me first. The first time, ask me where the video project is and which MP4 is the latest export. Install ffmpeg or Pillow first if either is missing. Every time I export a video after that: 1. Pull frames from the exported MP4 and stamp each one with its time (if ffmpeg has no drawtext, use Pillow). hook-reviewer gets frame 0 and the frames from the first 3 seconds. motion-reviewer gets contact sheets at 4 frames per second, plus the first and last frames. content-reviewer gets a full-size frame for every caption, a set at phone width, and the paths to the caption script and source material. 2. List issues as 'time · P0/P1/P2 · issue · fix', and have each one end with a score from 1 to 10. 3. Fix P0s first, then P1s, re-render, and save it as a new version (v1, v2…). Save each round's issues, scores and the 3 subagents' agent IDs in a review/ folder. 4. Use SendMessage with each agent ID to have the same subagent review the new version. Don't start new ones. They check last round's issues first. Once all 3 score 7 or higher, or after 3 rounds of review, stop and hand it to me. Start fresh subagents for the next video. Show me the files you'll create first, and don't write them until I confirm."
"在 ~/.claude/agents 下创建 3 个审查者子智能体,分别对应上述三个组:hook-reviewer、motion-reviewer 和 content-reviewer。使用 opus 模型,设置 effort 为 high,并仅赋予它们 Read、Glob 和 Grep 权限。它们只负责审查,绝不编辑。在每个智能体的 frontmatter 中,写入 experimental:,并在下一行缩进写入 cacheTtl: 1h。如果我的 Claude Code 版本低于 2.1.248,或者我的设置中已配置 subagentPromptCacheTtl,请先告知我。 首次使用时,询问我视频项目的位置以及哪个 MP4 是最新导出的文件。如果缺少 ffmpeg 或 Pillow,请先安装。 此后每次我导出视频时: 1. 从导出的 MP4 中提取帧,并为每一帧打上时间戳(如果 ffmpeg 没有 drawtext 功能,则使用 Pillow)。hook-reviewer 获取第 0 帧以及前 3 秒内的帧。motion-reviewer 获取每秒 4 帧的接触表(contact sheets),加上第一帧和最后一帧。content-reviewer 获取每个字幕对应的一张全尺寸帧、一套手机宽度的帧,以及字幕脚本和源素材的路径。 2. 将问题列为 '时间 · P0/P1/P2 · 问题描述 · 修复方案',并确保每条问题末尾附带一个 1 到 10 的评分。 3. 先修复 P0 级别的问题,然后修复 P1 级别的问题,重新渲染,并保存为新版本(v1、v2……)。将每轮审查的问题、评分以及 3 个子智能体的 agent ID 保存在 review/ 文件夹中。 4. 使用 SendMessage 配合每个 agent ID,让相同的子智能体审查新版本。不要启动新的智能体。它们会先检查上一轮的问题。一旦所有 3 个智能体的评分均达到 7 或以上,或经过 3 轮审查后,停止操作并将结果交给我。为下一个视频从头启动新的子智能体。 先向我展示你将创建的文件列表,在我确认之前不要写入任何文件。"
更进一步:量化金融体系
看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力