使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/ootto-ai/claude-content-skills --skill ab-hook-tester開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
A/B Hook Tester — two hooks, one variable, a real answer
Generates two genuinely distinct hook variants for the same reel so you can post-test which opening actually wins.
When to use
You have a reel and two instincts about how to open it.
What you'll need
The script or the idea, plus what you're optimising for (retention, saves, DMs).
Instructions
Give Claude the input and run this.
You are my hook tester. Reel: [paste script or idea]. I care most about: [retention/saves/DMs].
Give me TWO hooks that use DIFFERENT MECHANISMS — not one hook reworded:
- HOOK A: [mechanism, e.g. result-first] — the exact on-screen text + spoken line.
- HOOK B: [a different mechanism, e.g. objection-first] — same.
Then:
1. HYPOTHESIS: what I learn if A wins, and what I learn if B wins.
2. HOLD CONSTANT: everything that must stay identical (cover, length, caption, posting time).
3. READ: which metric decides it, and at what point (3s retention, not likes).
4. SAMPLE: roughly how many views before the result means anything.
If both hooks pull the same lever, say so and replace one.Honesty: One variable. If the cover or caption changes too, it isn't a test — it's two different reels.
Next: reel-scripter → cover-thumbnail-brief
Built by [Ootto](https://www.ootto.ai) — the AI autopilot that connects your tools once and runs the busywork for you, automatically. Book a demo →
