Back to Details

yt-comment

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

yt-comment

yt-comment

The comment section is a retention surface, not a chore. Replies in the first few hours are what decide whether a thread becomes a conversation other people read.
评论区是一个用户留存阵地，而不是一项杂务。最初几个小时的回复决定了评论串会变成一场其他人也会阅读的对话。

Before you write

开始撰写之前

  1. Read 
    ~/.claude/youtube/voice.md
    if it exists. That is the user's voice profile: how they talk on camera, the words they never use, who they are talking to, what they will not claim. If it does not exist, ask for three of their own videos, read or transcribe them, infer the voice, and write the file. A script in the wrong voice is worse than no script, because they have to read it out loud.
  2. Never invent a number, a result or a source. If a figure would strengthen it and you do not have one, ask for it or write the line without it.
  1. 如果 
    ~/.claude/youtube/voice.md
    存在，请先阅读它。这是用户的口吻档案：他们在镜头前如何说话、从不使用哪些词、面向哪些受众，以及不会作出哪些声明。如果该文件不存在，请向用户索取他们自己的三个视频，阅读或转录视频，推断其表达方式，然后编写该文件。口吻错误的脚本比没有脚本更糟糕，因为用户必须把它大声念出来。
  2. 绝不编造数字、结果或信息来源。如果加入某个数据会增强回复效果，但又没有可用数据，就向用户询问，或者不写相关内容。

Triage first, always

始终先做分流

Sort what the user pastes into four piles and say how many are in each before writing anything:
  1. Questions - answer them. These are your next video's topics, so note the repeats.
  2. Corrections - if they are right, say so plainly and thank them. Never argue a fact you cannot check.
  3. Praise - reply to a few, briefly, with something specific from their comment. A wall of identical "thank you!" replies reads as automated because it is.
  4. Bait - do not reply. Say so and move on. Never write a comeback, however deserved.
将用户粘贴的内容分成四类，并在开始撰写前说明每一类有多少条：
  1. 问题——回答这些问题。它们会成为下一个视频的选题，因此要记录反复出现的问题。
  2. 纠正——如果对方是对的，就坦率承认并致谢。绝不要争论一个无法核实的事实。
  3. 称赞——简短回复其中几条，并提到评论中的具体内容。一整排千篇一律的“谢谢！”回复会显得像是自动回复，因为它们确实是。
  4. 挑衅——不要回复。明确说明并继续处理其他评论。绝不要写反击内容，无论对方多么值得回应。

Writing the reply

撰写回复

  • Under 30 words. A long reply in a comment thread is a blog post nobody asked for.
  • Answer the actual question in the first sentence.
  • One question back, only when it is real.
  • No emoji unless the user's own replies use them. Check their voice file.
  • Never promise a video you have not agreed to make.
  • 控制在 30 个词以内。评论串中的长回复就是一篇没人要求的博客文章。
  • 在第一句话中直接回答真正的问题。
  • 最多追问一个问题，而且只在确有必要时追问。
  • 除非用户自己的回复会使用 emoji，否则不要使用。检查其口吻档案。
  • 绝不承诺制作一个尚未商定要做的视频。

The heart and the pin

点赞与置顶

Say which ONE comment to pin and why. Pin the question the most people also have, not the nicest one. Heart generously - it costs nothing and it is visible.
说明应该置顶哪一条评论以及原因。置顶大多数人也都想问的问题，而不是最好听的那一条。要慷慨地点赞——这不会产生任何成本，而且所有人都能看到。

The gate

发布关卡

Nothing here publishes. This skill writes and you publish. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?
这里的内容不会自动发布。这个 skill 负责撰写，由用户负责发布。每项输出都以一个供用户复制的文本块结束，并且每次运行的最后一行都是同一个问题：发布，还是修改？