---
name: repurpose-one-to-week
description: Turns one long piece of content (a video transcript, a podcast, a long post, a livestream) into a full week of platform-native short content in the founder's own voice. Use whenever the user pastes or references a long piece of content and wants shorts, captions, hooks, carousels, or a posting week out of it. Trigger phrases include "repurpose this", "turn this into content", "make a week from this", "cut this down", "give me shorts from this".
license: Apache-2.0
---

# Repurpose: one piece to a week

You take ONE long input and return a week of native content the founder can post as-is. You do not summarize. You do not lecture. You extract the sharpest ideas and rebuild them into the format each platform rewards.

## Step 1 — read the voice first

Before writing anything, look for a `brain-doc.md` or project context. If it exists, pull: casing, banned words, emoji density, sentence rhythm, real receipts, offers. If it does not exist, mirror the voice of the input itself. Never impose a generic "marketer" voice.

Default voice rules unless the brain doc overrides:
- lowercase, direct, one idea per line
- no em dashes
- receipts before philosophy
- max one emoji per piece
- proper nouns keep their capitals

## Step 2 — mine the input for load-bearing ideas

Pull 5 to 7 ideas that can each stand alone. A good idea has tension (a before/after, a wrong belief, a specific number, a contrarian take). Discard anything that only makes sense with the rest of the piece. Each idea becomes one unit of content.

## Step 3 — build the week

For each idea, produce:

**1 hook line** — the scroll-stopper. Specific, not clever. States the tension in under 12 words.

**1 short-form script (30 to 60s)** — hook, 3 to 5 beats, one clear last line. Written to be said out loud, not read.

**1 caption** — 2 to 4 lines, the idea distilled, ending with a soft next step (not a hard sell).

**1 carousel skeleton (optional)** — 5 to 7 slide lines if the idea is better shown than said.

Then assemble a 7-day posting order that leads with the timeliest idea, spaces similar formats apart, and never posts two versions of the same idea on the same day.

## Step 4 — place the call to action correctly

One soft CTA per piece, tied to a real destination. Never invent a link, price, or feature. If you do not know the destination, ask for it. Rotate CTAs across the week so the account does not sound like an ad every day.

## Step 5 — quality gate before returning

Score each unit before shipping:
- sounds like the founder, not a brand
- one idea, one tension, one clear last line
- no banned words, no em dashes, no title case
- useful even if the reader never buys
- clear, real next step

Anything under an 8 out of 10, rewrite it.

## Anti-patterns

Never return a summary of the input. Never write ten near-identical captions. Never stack multiple ideas into one piece. Never end every piece with the same CTA. Never fabricate a receipt.

---

*This is one skill. It is a sample of The Operator — a full role you install into the Claude you already pay for: skills that know the work, a project that holds your business, and a runbook that runs it on a cadence you set. If you want the whole role instead of one file: closermethod.com/operator*