Three one-time unlocks buy almost total automation.
1. Install the Claude in Chrome extension (~2 min) — Studio has no API for promos, thumbnail tests, pins, or community posts; the extension gives me your signed-in Studio, which unlocks all four, forever.
2. Answer one question: how does roguecanon.com currently get published? (There's no git repo or deploy config in the website folder — so today, only you know.)
3. Keep exactly one human job: taste. You approve every cut before it ships. Everything around that approval is machine work.
The weekly list, mapped
| Task | Automation path | Owner |
|---|---|---|
| Pause the four promos | No API exists. Via Chrome extension I click through Studio. Until then: 4 clicks by hand. | UNLOCK 1 then CLAUDE |
| Thumbnail Test & Compare ×2 | Studio-only feature. Extension lets me create both tests and upload your prepared A/B/C thumbs; results read back via CTR in the daily check. | UNLOCK 1 then CLAUDE |
| Deploy the site (chant sheets) | Unknown pipeline → tell me how it publishes. If it's git/Netlify/FTP, a CC prompt (or I) wire it to one command. Long-term: migrate to PageMotor per your existing import file — then I deploy by MCP with no pipeline at all. | UNLOCK 2 then CLAUDE/CC |
| Cut S1 (and all matchday Shorts) | I can cut video myself — ffmpeg in my sandbox + your mounted masters + your hand-timed .sbv karaoke files + your own deterministic-assembly methodology (assemble-the-pit.sh). I produce the draft; you watch it once. | CLAUDE + KENN approves |
| Upload & schedule Shorts | videos.insert via API with publishAt — approved cuts upload private and auto-publish 3h before each fixture. The matchday calendar literally runs itself. (May need one 2-min re-auth to add the upload scope.) | CLAUDE |
| Full-time result cut | Can't pre-schedule (depends on the score). Two pre-cut variants (win/defiance) sit ready as private uploads; publishing the right one at FT = one API call I make same evening, or one tap by you. | CLAUDE or KENN (1 tap) |
| Sunday community poll | No API for community posts. Extension + scheduled task = auto-posted Sunday evenings (needs your Mac awake with Claude open). Fallback: 2 min on your phone. | UNLOCK 1 then CLAUDE |
| Chant-sheet links into descriptions + pinned comments | Descriptions: pure API. Pinned-comment edits: also API (comments.update keeps the pin). Fires the moment the site is live. | CLAUDE |
| Comment replies, daily | 8am check flags; drafts in brand voice; you approve text once per reply (public speech stays gated) — or set a standing style rule and I post matching replies. | CLAUDE + approval |
| Weekly analysis | Already automated — daily 8am check + these hub reports. | CLAUDE |
What only Kenn can ever do
Approve creative (30 seconds per cut — the IG video proved this gate earns its keep) · install the extension · answer the deploy question · make the music. That's the whole list. Passwords, OTPs and payment things also stay yours by design — I don't touch credentials.
Where Claude Code fits
CC is the executor on your Mac for the two things outside my reach: the site deploy pipeline (once you name it, one CC prompt wires “deploy roguecanon.com” to a single command) and heavy local renders if we ever outgrow sandbox ffmpeg. Everything else — API, Studio-via-extension, PageMotor, analysis, scheduling — runs through me directly. I'll write any CC prompt the moment it's needed.
The steady state, once unlocked
Fixture list feeds the calendar → I pre-cut matchday variants from your masters → you approve a batch in one sitting → they upload private with scheduled publish → 8am check watches retention, CTR tests, comments and subs → flags land in your morning summary → you make music and approve cuts. Your weekly hands-on time: roughly 30 minutes.