Skill: cellinlab/cell-hook-optimizer (version 0.1.0)

--- name: hook-optimizer description: Hook and opening optimization for Chinese short-form content. Use when Codex needs to diagnose why the first 3-5 seconds or first 2-3 sentences are weak, determine whether the real problem is the opening or the material underneath it, and generate multiple opening directions that match the actual content instead of empty clickbait. metadata: {"openclaw":{"homepage":"https://github.com/cellinlab/cell-skills/tree/main/skills/hook-optimizer"}} --- # Hook Optimizer ## Overview Use this skill when the user already has a topic, body, or draft, but the opening is not doing enough work. The opening should help the audience answer three questions quickly: - what is this about - why should I continue - why should I trust or care about this voice This skill diagnoses first and generates later. ## Quick Start 1. Check whether the content underneath the opening is strong enough. 2. Extract the best available materials before rewriting the opening. 3. Diagnose the current opening if one exists. 4. Generate several opening directions, not one magic line. 5. Pick the strongest direction based on fit, not on loudness. If the content itself is too thin, say so before generating hooks. ## Default Contract Assume the following unless the user says otherwise: - write in Chinese - optimize the opening, not the whole piece - diagnose before generating - prefer openings that the body can actually cash - for spoken scripts, keep mouth-feel and breath rhythm in mind ## Workflow ### Phase 1: Read the Input State Determine whether the user provided: - an existing opening and a full body - only the body - a topic plus a few key materials If the user only gave a title-like topic with no body or material, say the input is too thin for serious opening work. ### Phase 2: Check Whether the Content Can Carry a Hook Look for usable fuel: - a result or concrete outcome - a contradiction or reversal - a strong scene or vivid moment - a number, comparison, or unusual detail - a direct judgment worth arguing with When the content has none of the above, say the hook will be limited because the body is under-fueled. Read [references/hook-principles.md](references/hook-principles.md) when deciding whether the problem is the opening or the content itself. ### Phase 3: Diagnose the Current Opening If the user already has one, check: - **independence**: can it work even if the title is unseen - **grip**: does it give the audience a reason to stay - **curiosity or tension**: does it hold something back - **credibility**: why believe or care about this speaker - **flow**: is it easy to say or read - **payoff fit**: can the body deliver what the opening promises ### Phase 4: Choose the Right Hook Type Select from the smallest set that truly fits: - result-led - contradiction-led - scene-led - question-led - judgment-led - suspense-led Read [references/hook-types.md](references/hook-types.md) when comparing directions. ### Phase 5: Generate a Hook Pack Produce 3-4 strategic directions. For each direction: - explain why it fits this content - generate 2-4 opening options - keep them distinct rather than slightly reworded copies If one direction clearly dominates, say so and explain why. ## Output Format Default to [assets/hook-pack-template.md](assets/hook-pack-template.md). At minimum, include: - content viability note - current opening diagnosis - extracted materials - multiple hook directions - top recommendations ## Hard Rules Do not: - pretend a weak body can be rescued by a flashy opening - depend on the title to complete the meaning - reveal the full answer too early when tension is needed - generate hooks the body cannot pay off - return one "best line" without showing alternatives Always: - diagnose before generating - extract the best available materials first - keep the opening aligned with the actual content - mention when the problem is upstream from the opening - preserve readability and speakability ## Resource Map - [references/hook-principles.md](references/hook-principles.md) - Read for the base rules of what a strong opening must do and how to detect weak-content cases. - [references/hook-types.md](references/hook-types.md) - Read for the main hook families, fit conditions, and failure modes. - [assets/hook-pack-template.md](assets/hook-pack-template.md) - Use for the standard output shape.

path: agents/openai.yaml
content: interface:
  display_name: "开头优化"
  short_description: "诊断前几秒或前几句为什么不够抓人，并生成多组可兑现的开头方案"
  default_prompt: "Use $hook-optimizer to diagnose this Chinese opening or short-form draft: determine whether the hook problem is really an opening problem or a weak-material problem, then generate multiple opening directions that the body can actually pay off."


path: assets/hook-pack-template.md
content: # 开头优化包

## 内容可做性判断

- 当前内容的素材充足度：
- 最适合拿来做开头的材料：

## 当前开头诊断

- Independence:
- Grip:
- Curiosity / Tension:
- Credibility:
- Flow:
- Payoff Fit:

## 可用素材

- 

## 开头方向 A

- 方向说明：
- 方案 1：
- 方案 2：
- 方案 3：

## 开头方向 B

- 方向说明：
- 方案 1：
- 方案 2：
- 方案 3：

## 开头方向 C

- 方向说明：
- 方案 1：
- 方案 2：
- 方案 3：

## 最推荐

- Top 1：
- Top 2：
- Top 3：


path: references/hook-principles.md
content: # 开头原则

## 1. 开头不是标题附属物

很多开头的问题，本质是它默认用户已经看了标题、封面或上下文。

强开头应该能独立完成最小沟通：

- 话题是什么
- 为什么现在要继续

## 2. 开头受正文约束

如果正文没有这些东西，开头的空间会明显变小：

- 结果
- 反差
- 场景
- 细节
- 明确判断

这时不要假装“换一句更炸的话”就能解决问题。

## 3. 开头不是答案区

很多开头失败，不是因为没信息，而是把信息交得太快，后面就没有推动力了。

常见修正：

- 从结论改成问题
- 从结论改成矛盾
- 从解释改成一个具体场景

## 4. 口播友好单独看

看起来像金句的句子，念出来不一定顺。

重点检查：

- 有没有太多书面连接词
- 句子是否太长
- 是否一口气能说完
- 节奏有没有变化

## 5. 开头要和正文签约

你在开头承诺的东西，正文最好真的会兑现。

失配示例：

- 开头像悬疑，正文却只是普通总结
- 开头像强判断，正文却没有支撑
- 开头像个人经验，正文却没有真实细节


path: references/hook-types.md
content: # 常见 Hook 类型

## 1. Result-led

适用：

- 有具体结果
- 有对比
- 有时间跨度

风险：

- 太像炫耀
- 结果和正文关系弱

## 2. Contradiction-led

适用：

- 有反常识
- 有认知冲突
- 观点能引发反驳

风险：

- 容易把答案直接说完
- 容易写得像空翻转

## 3. Scene-led

适用：

- 有画面
- 有人物
- 有具体时刻

风险：

- 进题太慢
- 场景好看但和主张不连

## 4. Question-led

适用：

- 读者已经有困惑
- 题目本身就是一个真实问题

风险：

- 问题过大
- 像课堂提问而不是吸引

## 5. Judgment-led

适用：

- 作者有鲜明观点
- 后面能提供支撑

风险：

- 像训人
- 只有态度没有材料

## 6. Suspense-led

适用：

- 有明显反转点
- 正文后面会给出关键解释

风险：

- 过度吊胃口
- 和正文落差太大


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)