content-repurposer

---
name: content-repurposer
description: Turn one long piece (article, post, transcript, talk) into a week of platform-native posts on a 7-day plan. Use when someone has one good piece and needs seven.
---

# Turn one piece into a week of posts

Nine pieces and a 7-day plan from one source, each rewritten for its platform.

## Claude does
1. Ask for: source (text or path), audience, two or three platforms, hub link, voice file or three past posts. Never guess the voice; a stale or time-sensitive source gets refreshed first.
2. Mine 5-10 atoms from the whole source (the best hide in asides and the second-to-last answer): one-liners, hard numbers, stories with a turn, contrarian moments, step fragments; one sentence plus verbatim excerpt each. Same hook, same idea. Under five: shorter week, said so. {ATOMS}
3. Pick the claim every piece carries. {CLAIM}
4. Map atoms to strongest format: story, LinkedIn; hard number, one X post; steps, carousel or thread; contrarian take, where that belief lives; demo moment, video. {FORMAT_MAP}
5. Write every first line to stand alone inside LinkedIn's 200-character fold or X's 280, led by the sharpest stat or contrarian take; no two alike. {HOOKS}
6. Schedule: strongest LinkedIn Monday, thread mid-week, carousel and video apart, no atom on adjacent days, X posts as extras, quotes for reposts and comments. Mark {FIRST}, usually the carousel. {SCHEDULE}
7. Fill CODEX.md, run the hand-off.

## Then Codex does
Codex drafts all nine pieces to platform limits, one file each, plus the plan table and leftovers: bulk drafting against decided inputs.

```
codex exec --sandbox danger-full-access --skip-git-repo-check -C "<working folder>" - < CODEX.md
```

Fill first: {WORKING_FOLDER}, {SOURCE}, {AUDIENCE}, {PLATFORMS}, {HUB_LINK}, {VOICE}, {ATOMS}, {CLAIM}, {FORMAT_MAP}, {HOOKS}, {SCHEDULE}, {FIRST}; {FIX} empty at first.

## Claude checks
1. Coverage: every atom used once or in leftovers; every draft names its atom and carries {CLAIM}; thread and newsletter end on a hub CTA; {FIRST} marked.
2. Copying: search drafts for five source sentences; any hit rejects. Quotes match the source exactly.
3. Limits: LinkedIn under 1,300 characters, no body link, ends on a question; thread 3-9 tweets under 280, two hashtags max; X posts none; carousel cover 8 words, slides 25; video hook 3 seconds, 60 total, text every beat; newsletter subject 40-60 characters, 150-200 words, one CTA.
4. Standalone and voice: "as I wrote", "in this week's", "episode", "part 1", third-person summary, hedging or a punched-up quote reject.
5. Failures go under {FIX}; rerun and recheck until all pass.

## Rules
- Never publish the source verbatim in a smaller format; rewrite every piece for its format. Repurposing is not crossposting.
- One consistent claim across the week; vary everything else.
- Mark which piece to post first if only ONE can be published, usually the carousel.
- Never pad a thin source, reuse an atom or self-reference a series.
- No LinkedIn body links, no "I'm excited to share", no tweet over 280, no slow video hook, no piece without a CTA or question.
- Never dump the batch at once or put carousel and video on one day.
- Two or three platforms, never five; mix in native posts; Reddit only with a question title, value inside, 10% self-promotion.
- Refresh stale pieces first; reshare winners every 3-6 months; resend to non-openers with a new subject line.
- Every piece points back to the hub; rented channels are not the destination.
- No publishing without a human read against the voice file.

## If Codex is not installed
Claude drafts the pieces itself, saves the same files, says so.

## Built from
- coreyhaines31/marketingskills: https://github.com/coreyhaines31/marketingskills/blob/main/skills/social/SKILL.md (46,908 stars, api.github.com, 5 Sep 2026)
- inklate/social-skills: https://github.com/inklate/social-skills/blob/main/skills/social-repurpose/SKILL.md (5 stars; structure, corroborated by the rest)
- megastep/codex-skills: https://github.com/megastep/codex-skills/blob/main/blog-repurpose/SKILL.md (4 stars; platform limits)
- Justin Welsh, 1-3-5 Method: https://www.justinwelsh.me/newsletter/how-1-piece-of-content-becomes-16-the-1-3-5-method (author's own site)
- Ross Simmonds, Create Once, Distribute Forever: https://dreamdata.io/blog/a-b2b-content-distribution-masterclass-with-ross-simmonds (book; Baer, Fishkin, Gerhardt endorse)
- Buffer repurposing guide: https://buffer.com/resources/repurposing-content-guide/ (vendor practice, updated 20 Jan 2026)

# Content repurposer - Codex task

## You are given
- {WORKING_FOLDER}: the folder to save everything in.
- {SOURCE}: the full original piece (post, article, transcript or talk).
- {AUDIENCE}: who reads it. {PLATFORM}: where it will be posted.
- {LINK}: the one link for the newsletter section.
- {CLAIM}: the one sentence every piece must carry.
- {POINTS}: the cover claim, five slide points, the surprising point (video), the contrarian point (Sunday post), the story behind the main point (newsletter), and the unanswered question.
- {HOOKS}: three opening lines, one per short post, each tied to its point.
- {VIDEO_STRUCTURE}: the 45-second beat structure to follow.
- {FIRST}: the piece to publish if only one can go out.

## Produce
Save these in {WORKING_FOLDER}/repurposed/, plain Markdown, British English, no em dashes, written for {AUDIENCE} on {PLATFORM}:

1. `00-schedule.md` - Mon carousel, Tue post 1, Wed video, Thu post 2, Fri newsletter, Sat quote card, Sun post 3. Mark {FIRST} as the piece to post if only one can be published.
2. `01-carousel.md` - 7 slides. Slide 1: cover with the biggest claim. Slides 2 to 6: one point each, a headline and one sentence. Slide 7: a close with a question or a comment-to-DM ask. Exact text per slide.
3. `02-post-1.md`, `04-post-2.md`, `07-post-3.md` - each takes ONE point from {POINTS} and makes it the whole post. Open with its line from {HOOKS}. Under 120 words each. Never the same first line. Post 3 is the contrarian one.
4. `03-video-script.md` - 45 seconds on the surprising point, following {VIDEO_STRUCTURE}. About 110 spoken words.
5. `05-newsletter.md` - 150 words: the point, the story behind it, and {LINK}.
6. `06-quotes.md` - five pull-quotes, each under 20 words, each standalone, for image cards or comments.
7. `08-question.md` - one comment-bait question the source raises but does not fully answer, for a text-only post.

## Rules
- Never publish the source verbatim in a smaller format. Every piece is rewritten for its format.
- Keep {CLAIM} consistent across the week so the audience notices the theme; vary everything else.
- Mark in the output which piece to post first if only ONE can be published - usually the carousel.

## Fix
{FIX}: empty on the first run. On a rerun, correct only what is listed here and leave every other file unchanged.

## Return
Print at the end:
- the full path of every file written;
- the word count of each post, the newsletter and the script;
- the first line of each of the three posts;
- the sentence in each piece that carries {CLAIM};
- any input that was missing and what you did instead.