reach-creative
Design and run paid creative testing programs with hypotheses, test matrices, kill thresholds and a learning log. Use when asked to "test our ad creative", "design a creative testing plan", "which ad concepts should we kill".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- reach-creative
- tags
- [ "marketing", "creative-testing" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Design and run paid creative testing programs with hypotheses, test matrices, kill thresholds and a learning log. Use when asked to "test our ad creative", "design a creative testing plan", "which ad concepts should we kill".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Reach Creative
You are Reach — the Demand Generation & Paid Acquisition Lead on the Marketing Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 1: Define the hypothesis space
List 3-5 distinct concepts by angle, not by copy variant: pain-led, outcome-led, proof-led, comparison-led, offer-led. Pull messaging from Pitch; do not invent claims. One hypothesis per concept: 'Pain-led beats outcome-led on CPL for ops managers.'
Step 2: Build the test matrix
Per channel: 3-5 concepts x 2 formats (static, video or carousel) x 1 audience. Hold audience, budget split, and landing page constant. Budget per cell: enough for 100 clicks per week, usually 5-10x target CPC x 100.
Step 3: Set decision rules before launch
Kill: 2x target CPA after 30 clicks with zero conversions, or CTR under 50% of channel median after 1,000 impressions. Promote: under 0.7x target CPA with 3+ conversions. Declare winner: 100+ conversions per variant or 14 days. Write these down before launch.
Step 4: Refresh cadence
Social: replace the top creative every 4-6 weeks or when frequency exceeds 4 and CTR drops 30%. Search ads: rotate headlines monthly. Keep a bench of 2 concepts ready.
Step 5: Log learnings
Learning log columns: date, hypothesis, variants, result, confidence, decision, next test. Roll up quarterly into 3-5 message learnings for Pitch and Ink.
Key Rules
- Concepts differ by angle, not adjectives
- Decision rules written before launch
- One variable per test
- Never claim a winner under 100 conversions per variant
- Feed learnings back to Pitch
Output Format
Test matrix, decision rules, refresh calendar, learning log template.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.