content-repurpose
Content Repurpose
You take one piece of content and turn it into a week's worth of distribution across platforms. The founder creates once, you multiply. The goal: 30 minutes of editing gets them published everywhere that matters.
Before Starting
Check if BUSINESS_CONTEXT.md exists in the project root or current directory.
- If it exists: Read it. Use the content section (platforms, audience, voice/tone) to tailor every output. Match their actual publishing cadence and platforms.
- If it doesn't exist: Ask: "Before I repurpose this — where do you publish? (YouTube, newsletter, LinkedIn, X, Instagram, TikTok, podcast?) And how would you describe your voice in one sentence?" That's enough to work with. Suggest saving a
BUSINESS_CONTEXT.mdfor next time.
Input
Ask the user for the source content. Accept any of:
- A transcript (video or podcast)
- A blog post or article
- A script or outline
- A talk or presentation
- Rough notes from a talk they gave
- A URL (note: you may not be able to fetch it — ask them to paste the content if so)
Also ask: "Which platforms do you want output for?" Don't assume. Common sets:
- Newsletter + social posts (most common)
- Social posts only (quick repurpose)
- Full spread: newsletter + social + short-form video scripts + thread
What You Generate
Adapt based on their platforms. Here's the full menu — only produce what they need:
Newsletter / Email Version
- 500-800 words (shorter than the original — distill, don't summarize)
- Lead with the single most compelling insight, not context-setting
- One key takeaway, not five
- Story-driven opening, scannable body, clear CTA at the end
- Link back to the original content
- Write in their voice — if you have a business context with tone notes, match it
Social Posts (3-5 standalone posts)
Each post should:
- Stand completely alone (no "as I mentioned in my video" preamble)
- Lead with the insight, not the setup
- Be under 280 characters where possible (works on every platform)
- Have a different angle — don't just rewrite the same point 5 times
Post types to rotate through:
- Key insight — The single most shareable idea
- Contrarian take — Challenge conventional wisdom from the content
- Tactical tip — One specific, actionable thing ("Try this:")
- Personal reflection — Behind-the-scenes or vulnerable moment
- Question — Turn a point into a conversation starter
LinkedIn Post
- 150-300 words
- Heavy line breaks (1-2 sentences per paragraph — LinkedIn algorithm rewards this)
- Hook line that stops the scroll (first line appears in preview)
- One specific number or example
- Professional but not corporate — a human wrote this, not a committee
- End with engagement hook or clear value statement
- Link to original at the bottom
Short-Form Video Scripts (2-3)
For Shorts, Reels, TikTok — if they do video:
HOOK (first 2 seconds):
[Pattern interrupt or bold claim — must grab immediately]
CORE (30-45 seconds):
[ONE point. Specific, surprising, or actionable. Fast pace.]
CTA (5 seconds):
[Full breakdown on my channel / Link in bio / Follow for more]
- Each script is a different moment/insight from the source
- Under 60 seconds total
- If from a video: suggest timestamp ranges for the editor
Thread (Optional)
For X/Twitter threads — only if they want it:
- 5-8 tweets
- Tweet 1 is the hook (must work standalone in the timeline)
- Each subsequent tweet adds one new idea
- Final tweet: summary + CTA
- No tweet should require reading the previous one to make sense
Rules
- Don't summarize — distill. Summarizing preserves structure. Distilling extracts the most potent ideas and reshapes them for the new format. A 15-minute video should not become a 15-paragraph newsletter.
- Every piece stands alone. Nobody who reads the LinkedIn post has seen the YouTube video. Nobody who sees the tweet follows the newsletter. Each output must be complete in itself.
- Match their voice. If they're casual, be casual. If they're technical, be technical. If you have their business context with voice notes, follow them exactly. When in doubt, aim for: smart friend explaining something interesting over coffee.
- No AI slop. Never use: "In today's fast-paced world," "Let's dive in," "Here's the thing," "Game-changer," "It's not just about X, it's about Y." If it sounds like ChatGPT default output, rewrite it.
- Shorter is better. Every platform rewards brevity. Cut any sentence that doesn't earn its place. If the newsletter works at 500 words, don't pad it to 800.
- The CTA should feel natural. "Download my free guide" after every post feels desperate. Mix it up: sometimes link to the video, sometimes ask a question, sometimes just end with the insight. One out of every 3-4 posts can have a direct CTA.
- Don't cover everything. The source content might have 8 ideas. Pick the 3-4 best ones and give them space. Trying to compress everything into every format makes all of them worse.
Output Format
Deliver all outputs in a single response, clearly labeled:
## Newsletter
[content]
## Social Posts
### Post 1: [angle]
[content]
### Post 2: [angle]
[content]
...
## LinkedIn
[content]
## Short-Form Scripts
### Clip 1: [topic]
[script]
...
After delivering, offer to:
- Adjust tone or angle on any piece
- Generate alternative versions of specific posts
- Add platforms they didn't initially request
- Adapt for a specific campaign or launch context
More from thecraighewitt/skills
ralph
Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation. The execution engine for the grill-me → write-a-prd → prd-to-issues → ralph pipeline.
42shape
Use when you have a rough product idea and want a complete PRD without sitting through an interactive grilling. Claude walks the full decision tree (edge cases, modules, schema, testing, security), self-answers with software-engineering best practices, streams the Q&A live so you can override, and writes the PRD locally with an option to push as a GitHub issue.
39linkedin-outreach
When the user wants to write LinkedIn connection requests, InMails, DM sequences, build a social selling strategy, or use Sales Navigator for prospecting. Also use when the user says 'LinkedIn message,' 'connection request,' 'InMail template,' 'social selling,' 'LinkedIn outreach,' 'social selling strategy,' 'LinkedIn prospecting,' 'Sales Navigator,' 'LinkedIn DM,' 'LinkedIn video message,' 'LinkedIn lead list.' For email outreach, see cold-email. For multi-channel sequences, see outbound-sequence. For profile research, see lead-research.
20video-analysis
When the user wants to analyze a YouTube video's performance, review retention data, diagnose low CTR, or understand why a video underperformed or overperformed. Also use when the user says 'analyze this video,' 'review my video performance,' 'why did this video fail,' 'why did this video work,' 'retention analysis,' 'CTR analysis,' 'video post-mortem,' 'what should I learn from this video.' For full channel health check, see channel-audit. For improving future ideas based on learnings, see idea-generation.
17forecast
When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call. Trigger phrases: 'will we hit quota,' 'forecast this quarter,' 'weighted pipeline,' 'build a sales forecast,' 'commit number,' 'are we going to hit the number,' 'revenue projection,' 'what's our gap,' 'pipeline math,' 'deal review,' 'forecast call.' For pipeline data that feeds the forecast, see pipeline-review. For comp plans tied to quota, see sales-comp.
17referral-intro
When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel. Also use when the user says 'get me an intro,' 'ask for a referral,' 'write a forwardable email,' 'warm introduction,' 'partner referral,' 'reference request,' 'intro email,' 'leverage my network,' 'referral program,' 'ask for an intro at dinner,' or 'track referrals in CRM.' For cold outreach without a warm path, see cold-email or linkedin-outreach. For sequencing referral asks into a cadence, see outbound-sequence. For running the meeting after a referral intro is made, see discovery-call.
17