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 · 答案(只给评分者,不给执行者)
## 必须抓到(4)
| # | 位置 | 类型 | 说明 |
|---|---|---|---|
| D1 | 第 3 段「你说坚持很重要…你说要复盘…」四连 | 手里有了还在给 | 同一个意思举了四个例子,第二个之后观众已经拿到了 |
| D2 | 第 4 段茶叶案例 → 第 5 段「那么第三个原因」 | 等的没来 | 案例结束没有收束句把它接回「第二个原因」,直接跳到第三个;观众在等「这个例子在说明什么」 |
| D3 | 第 5 段「你以为…其实…」三连 | 正在给的听不清 | 自问自答连用三次 |
| D4 | 第 6 段「针对上述…鉴于…基于以上…即…」 | 正在给的听不清 | 单句超 60 字 + 纸面词四个 |
## 不许误报(2 个陷阱)
| # | 位置 | 为什么不是问题 |
|---|---|---|
| T1 | 第 2 段「看这里,我在板上画个圈」「划重点啊」 | 白板稿,这两句在指挥观众看板书,不是空转 |
| T2 | 第 4 段整段茶叶案例 | 看起来跑题(从「三个原因」跳去讲茶叶),但它是第二个原因的证据,遮掉之后「说的都对为什么不涨」就只有断言没有例子。承重墙,不能建议删 |
## 评分
- 命中 D1–D4 每个 1 分;误报 T1 / T2 任一扣 1 分;把 T2 标成「可删」扣 1 分
- 满分 4。新版 ≥ 旧版即通过
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 |