사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/ootto-ai/claude-content-skills --skill ab-hook-tester시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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 →
