Content Repurposer — one asset becomes ten — Claude Skill
A Claude Skill for Claude Code by Gooseworks — run /content-repurposer in Claude·Updated
Turn one long-form asset into 10+ derivative pieces
- Takes a long-form asset and produces 10+ derivative pieces
- Generates LinkedIn posts, X threads, and email snippets
- Creates short-form hooks and pull-quotes per asset
- Pure reasoning skill — no scraping or scripts
- Works with blog posts, webinars, podcasts, and articles
Who this is for
What it does
Get 10x distribution per blog post without writing each variant from scratch.
Founders post one long-form thought and get a week's worth of social copy out of it.
Turn every podcast into LinkedIn posts, threads, pull-quotes, and email snippets.
How it works
Take a long-form asset as input (blog, transcript, article)
Identify the core ideas and most quotable moments
Generate format-specific variants for each channel
Adjust tone per channel (casual for X, formal for LinkedIn)
Output a complete distribution kit
Metrics this improves
Want to use Content Repurposer?
Choose how to get started.
Install and run this skill locally on your computer.
Open a terminal on your computer and paste this command:
This downloads the skill with all its files to your computer:
Add -g at the end to make it available in all your projects.
Start Claude Code, then type the command:
Content Repurposer
Pure reasoning skill. Takes one long-form asset and fans it out into 10+ channel-specific derivative pieces — all aligned to the author's brand voice.
When to Use
- "Turn this blog post into LinkedIn content"
- "Repurpose this webinar into tweets and an email"
- "I have a podcast episode, help me get more mileage from it"
- "Turn this into posts I can schedule for the next two weeks"
Phase 0: Intake
Ask all questions at once, organized clearly. Keep it fast — this skill should feel frictionless.
Source Content
- Paste the content OR share the URL (blog post, LinkedIn article, transcript, etc.)
- What is the core insight or argument of this piece? (Summarize in 1-2 sentences)
Author Context
- Who is the author? (Title, company, area of expertise)
- What is their tone? (Casual/direct, professional, storytelling, data-driven — or share a sample post)
- Who is the audience? (ICP title, industry, stage)
Output Preferences
- Which channels do you want output for? (LinkedIn, Twitter/X, email snippet, or all three — default: all)
- Any specific hooks, stats, or quotes from the piece that must be included?
Phase 1: Extract Source Intelligence
Before writing any variants, extract the following from the source content:
- Core thesis — The single most important claim or insight
- Top 3 supporting points — Evidence, examples, or sub-arguments
- Best data/stats — Numbers, percentages, benchmarks
- Best quotes — 2-3 pull-quote candidates
- Contrarian angle — What conventional wisdom does this challenge?
- Specific examples — Named companies, people, tools, events
- Emotional hook — The frustration, aspiration, or fear this piece speaks to
Phase 2: Generate Derivative Pieces
LinkedIn Posts (generate 4-5 variants)
| Type | Structure | Length |
|---|---|---|
| Insight post | Hook → 3 supporting points → CTA | 150-300 words |
| Listicle | Hook → numbered list (5-10 items) → close | 200-350 words |
| Contrarian take | Unpopular opinion → why → evidence → implication | 100-200 words |
| Personal story | Situation → problem → turning point → lesson | 150-250 words |
| Data post | Stat hook → context → implication → question | 80-150 words |
LinkedIn formatting rules:
- First line must hook without finishing the sentence (forces "see more")
- Use line breaks liberally — one idea per line for scanability
- No bullet points in first 3 lines
- End with a question or call to reflect — not a CTA to buy
- Emojis optional — match the author's existing style
Twitter/X Thread (generate 1-2 threads)
- Thread length: 5-8 tweets
- Tweet 1: The payoff, not the setup. State the insight directly.
- Tweets 2-6: One supporting point per tweet. Short, punchy.
- Tweet 7: Callback to tweet 1 with reframed conclusion
- Tweet 8 (optional): Soft CTA — "I wrote about this in depth: [link]"
Each tweet: max 240 chars. No jargon. End threads with the strongest line.
Email Snippet (generate 1-2 variants)
Format for use in newsletters, nurture sequences, or cold outreach PS lines.
| Type | Length | Use Case |
|---|---|---|
| Newsletter blurb | 80-120 words | Weekly digest, newsletter intro |
| PS line | 20-40 words | Cold email personalization layer |
Short-Form Hooks (generate 5-8 standalone hooks)
One-liner openings that work across contexts. Can be used to A/B test posts or as standalone comments.
Examples of good hooks:
- "Most [role]s get [topic] completely backwards."
- "The [thing everyone does] is why [bad outcome]."
- "[Number] years ago, [company/person] did [thing]. Here's what happened."
- "Unpopular opinion: [claim]."
- "The real reason [common problem] happens isn't [assumed cause]."
Pull-Quotes (generate 3-5)
Shareable quotes formatted for screenshots or image posts. Should stand alone without needing context.
Phase 3: Review & Deliver
Present outputs organized by channel:
## Source Summary
Core thesis: [1 sentence]
Top 3 points: [bullets]
## LinkedIn Posts
### Post 1 — [Type]
[Full post text]
### Post 2 — [Type]
[Full post text]
...
## Twitter/X Thread
Tweet 1: [text]
Tweet 2: [text]
...
## Email Snippets
### Newsletter Blurb
[text]
### PS Line Options
- [option 1]
- [option 2]
## Short-Form Hooks
1. [hook]
2. [hook]
...
## Pull-Quotes
> "[quote]"
> "[quote]"
Iteration Rules
- User picks their 2-3 favorite variants → refine only those
- Max 2 rounds of revision per channel
- If the author has existing posts to match, ask them to paste 1-2 examples before generating
Tools Required
None. Pure reasoning. Works with any LLM agent.