Analyze Videohao Viral Posts

Analyze Videohao Viral Posts

Workflow

1. Identify the available inputs: cover image, title text, transcript, script document, influencer profile, platform, content scene, product, and campaign goal.
2. Read references/analysis-framework.md before producing the analysis.
3. If the user provides an image, inspect it directly. Capture visible text, subject/persona, scene, product/logo exposure, visual hierarchy, and emotional signal.
4. If the user provides only a title without a cover image, analyze the title and state that visual cover cues are unavailable.
5. If the user provides a transcript or script, analyze the content structure from the actual wording. If both are missing, provide only cover/title analysis and ask for transcript only when content analysis is required.
6. Output in Chinese unless the user requests another language.

Default Output

Use this two-section format by default:

### 封面&标题解析
[1 concise paragraph explaining audience filtering, click trigger, persona/scene/visual mechanics, and title hook.]

### 内容分析
[1 concise paragraph explaining opening hook, pain or curiosity setup, product introduction path, concrete feature demonstration, emotional value, and ad-feel control.]

For multiple posts, repeat the two sections under each item name, such as ## 达人名 / 场景.

Analysis Standards

• Explain the mechanism, not just the content. Prefer "通过 X 让 Y 人群产生 Z" over "内容很吸引人".
• Anchor every judgment in observable evidence from the cover, title, transcript, or script.
• Prioritize ad-operations usefulness: who is filtered in, why they click, why they keep watching, how the product is introduced, which selling point is proven, and how hard-sell feeling is reduced.
• Keep each section close to the style of the provided examples: usually 1 paragraph, direct, specific, and operational.
• Treat examples and named scenes in the reference as calibration samples, not allowed categories. Generalize to any similar 视频号爆文 by identifying the underlying mechanism.
• Do not output a generic "爆文公式总结" unless the user explicitly asks for formulas or patterns. This skill focuses on per-post analysis.
• Do not invent cover details when no image is provided. Do not claim a script-document detail was read if only a title or transcript was supplied.

Iteration Protocol

• Do not update or "沉淀" this skill after ordinary analysis requests, even if the user gives feedback on one output.
• Treat feedback as current-conversation guidance unless the user explicitly asks to update,沉淀,固化,写进 skill, or "以后都这样".
• When the user asks to沉淀, first summarize the proposed reusable changes and ask for confirmation before editing files.
• In the confirmation summary, state: what will be added or changed, which file will be edited, the intended scope, and what existing capability will be preserved.
• After confirmation, prefer additive, scoped updates over replacing broad rules. Generalize from repeated or clearly reusable feedback; avoid writing one-off preferences as universal rules.
• Keep the skill concise. Merge duplicate guidance, avoid long raw examples, and validate the skill after edits.

Resource

• references/analysis-framework.md: detailed dimensions, case-derived patterns, sentence templates, and quality checks for 视频号爆文分析.