Skip to content

ZJU-REAL/Easel / skills/builtin/skill-content-postmortem

skill-content-postmortem

Verified

内容复盘与爆款规律提炼。两种模式:(A) 单条复盘 — 分析一条已发布内容为什么爆/扑, 从 Hook、结构、选题、时间、平台适配等维度拆解原因;(B) 规律提炼 — 从多条内容中 提炼爆款共同特征、总结可复制的爆款公式。当用户说"这条为什么火了"、"为什么扑了"、 "复盘"、"分析数据"、"爆款规律"、"总结规律"、"爆款公式"、"内容复盘"、"什么规律"时触发。

FileKindSize
EASEL-META.mdmarkdown1.4 KB
SKILL.mdskill md8.0 KB
references/postmortem-dimensions.mdmarkdown1.9 KB
scripts/aggregate.pyscript8.3 KB

references/postmortem-dimensions.md

View on GitHub
# 内容复盘评估维度详解

## Hook 力(前 3 秒 / 首屏吸引力)

| 分数 | 标准 |
|------|------|
| 1-3 | 开头平淡无吸引力,无悬念/冲突/利益点,用户大概率划走 |
| 4-6 | 有一定吸引力但不够强,开头信息密度低或节奏慢 |
| 7-8 | 开头有明确钩子(提问/冲突/数据),能让多数目标用户停留 |
| 9-10 | 前 3 秒即产生强烈好奇/共鸣/冲突感,完播率/阅读率远超同类 |

## 内容结构

| 分数 | 标准 |
|------|------|
| 1-3 | 逻辑混乱,信息堆砌,无清晰主线 |
| 4-6 | 有基本逻辑但节奏平,缺少起伏和转折 |
| 7-8 | 结构清晰,节奏有变化,信息密度适中 |
| 9-10 | 结构精巧,每个段落都有存在价值,节奏感强 |

## 信息密度

| 分数 | 标准 |
|------|------|
| 1-3 | 大量废话/重复,或过于简略缺乏干货 |
| 4-6 | 信息量尚可但有冗余段落 |
| 7-8 | 信息量充足且紧凑,没有明显水分 |
| 9-10 | 每句话都有信息增量,干货密度极高 |

## 互动引导

| 分数 | 标准 |
|------|------|
| 1-3 | 无任何互动引导,评论区冷清 |
| 4-6 | 有简单引导("点赞关注")但缺乏互动话题 |
| 7-8 | 有明确的互动问题或争议点,能引发讨论 |
| 9-10 | 互动设计精巧,评论区自发产生二次传播内容 |

## 视觉/排版

| 分数 | 标准 |
|------|------|
| 1-3 | 排版混乱/画面粗糙,影响阅读/观看体验 |
| 4-6 | 基本整洁但无设计感 |
| 7-8 | 视觉舒适,有品牌一致性 |
| 9-10 | 视觉本身就是传播力,用户愿意截图/分享 |

## 平台适配

| 分数 | 标准 |
|------|------|
| 1-3 | 明显不适合该平台的内容形式/调性 |
| 4-6 | 基本适配但未利用平台特有功能/算法偏好 |
| 7-8 | 充分利用平台机制,格式/标签/时长都到位 |
| 9-10 | 深谙平台规则,内容形式与平台算法高度契合 |
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall