iamzifei/aikey / skills/aikey-flow
aikey-flow
VerifiedAI KEY·哪里会被划走 ——口播稿「划走点」专项。替观众把稿子听一遍:每一拍观众手里有什么、在等什么,断在哪一拍 —— 等的没来、手里有了还在给、正在给的听不清。诊断完默认主动问是否标记式改稿。不负责发布红线和能不能发(→ aikey-review)、内容戳不戳人(→ aikey-resonate)、单独换开头或标题(→ aikey-hook / aikey-title)。 触发方式:/aikey-flow、/会不会划走、/顺稿、/aikey-顺稿、「这稿子顺不顺」「哪里会划走」「逻辑有没有断」「读起来卡不卡」「完播会不会掉」 Drop-off check for talking-head scripts: walk the script as a listener, beat by beat — what the viewer holds, what they are waiting for, and where that chain breaks. Not for: red lines and publish-readiness (aikey-review), whether it resonates (aikey-resonate), replacing just the opening or title (aikey-hook / aikey-title). Trigger: /aikey-flow, "does this script flow", "where will viewers drop off", "check retention risk" —— AI KEY · 不给公式,给判据。每条规则都标了实测代价。
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.0 KB |
| evals/README.md | markdown | 1.1 KB |
| evals/sample-01-白板稿.md | markdown | 1.9 KB |
| evals/sample-01-答案.md | markdown | 1.4 KB |
| evals/sample-02-口播稿.md | markdown | 1012 B |
| evals/sample-02-答案.md | markdown | 1.2 KB |
| references/规则卡.md | markdown | 4.7 KB |
evals/sample-01-白板稿.md
View on GitHub# 测试稿 01 · 白板视频
载体:白板 / 手写视频(作者已声明)
---
为什么你一个月发了三十条视频,粉丝还是不涨?我今天把这件事讲透,三个原因,你对着看自己中了哪一个。
先看第一个。你发的每一条,观众都记不住你是谁。看这里,我在板上画个圈,圈里是你,圈外是所有跟你讲同一类东西的人。观众刷到你的时候,他分不清你和圈外那些人的区别,他今天看了明天就忘。划重点啊,记不住不是内容差,是没有一个你独有的说法。
第二个原因,你每一条讲的东西都是对的,但都是大家已经知道的。举个例子,你说「坚持很重要」,没人反对,也没人记得。你说「早起效率高」,没人反对,也没人记得。你说「要有目标」,没人反对,也没人记得。你说「要复盘」,没人反对,也没人记得。正确的话,观众听完等于没听。
去年我帮一个卖茶叶的朋友看账号。他的视频全是茶叶的产地、工艺、冲泡温度,专业得不得了,三个月涨了四百个粉。后来他把一条视频改成「我劝你别买明前茶」,一条涨了两千。这不是他的茶变了,是观众终于有了一个记住他的理由。
那么第三个原因是什么呢?第三个原因就是你的开头。你以为开头是打招呼吗?其实开头是筛人。你以为开头越亲切越好吗?其实开头越尖越好。你以为大家都这么开头就对吗?其实大家都这么开头就是错的。
针对上述三个原因,鉴于当前短视频平台的推荐机制已经从关注分发全面转向兴趣分发,基于以上分析,我们可以得出如下结论,即创作者应当优先解决记忆点缺失的问题。
所以回到开头那个问题。三个原因,记不住你、说的都对、开头没筛人。你先改第一个。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |