The Content Repurposer: Turn One Blog Post Into Platform-Native Posts That Don't Read Like Copies of Each Other
Why this prompt matters
Teams that copy-paste the same wording across platforms see dramatically lower engagement, because the phrasing that works on LinkedIn reads flat on X and gets scrolled past on Instagram — each platform's audience has different scroll habits and expects a different kind of hook. Marketers who repurpose lazily end up training their own audience to skip their posts, because a follower who sees the identical sentence on two platforms in one day learns that the second one is never worth stopping for.
What we use it for
A content marketer just published a 1,500-word blog post on why remote-work productivity metrics are broken, and has 30 minutes before their social scheduling tool's weekly queue locks. They need native, non-duplicate posts for LinkedIn, X, and an Instagram caption that each stand alone and drive clicks back to the full piece, without just pasting the same paragraph into three different boxes.
Prompt
Role: Act as a social media content strategist who specializes in adapting long-form content for different platform audiences without losing the original's substance. Context: - Source content: [PASTE FULL BLOG POST OR ARTICLE HERE] - Target platforms: [E.G., "LinkedIn, X/Twitter, Instagram caption"] - Brand voice notes: [E.G., "direct and slightly irreverent, no corporate jargon, short sentences"] - Primary goal for this content: [E.G., "drive traffic back to the full article" OR "establish thought leadership" OR "generate discussion in the comments"] Task: 1. Identify the 3-5 most shareable, standalone ideas within the source content — each one should work without requiring the reader to have read the full article. 2. For each platform in [TARGET PLATFORMS], write one native-feeling post per idea (not the same post copy-pasted across platforms) that: - Opens with a hook suited to that platform's scroll behavior (a question, a contrarian statement, a specific number — vary the hook type across posts). - Respects that platform's typical length, tone, and formatting conventions (line breaks, hashtag use, character limits). - Ends with a call-to-action appropriate to [PRIMARY GOAL]. 3. Label each output with which specific idea from the source it's built around, and which psychological hook it uses (curiosity gap, social proof, contrarian take, specific number/stat, etc.). Constraints: - Do not simply shorten the original text — reframe each idea for how people actually consume that specific platform. - Vary the hook type across the full set; do not reuse the same opening pattern (e.g., "Did you know...") more than once. - Do not fabricate statistics, quotes, or claims that are not present in the source content. - Match the brand voice notes exactly, and flag it if the source content's tone conflicts with the stated brand voice. Output Format: For each post, output: **[Platform Name]** Post: [the actual post copy, ready to publish] Built from: [which idea or section of the source this is drawn from] Hook type: [the psychological trigger used]
Result
LinkedIn
Post: Most remote teams are measuring the wrong thing. Time-tracking software tells you someone was active for 7.5 hours. It tells you nothing about whether those hours produced anything. In our audit of 40 remote teams, the ones with the highest “active time” scores shipped 23% less than teams that tracked outcomes instead. If your team's productivity dashboard is measuring keystrokes and mouse movement, you're optimizing for the appearance of work, not the output of it. What would your team's numbers look like if you swapped activity tracking for a weekly outcomes review instead?
Built from: the section comparing activity-tracking software results against team output data
Hook type: contrarian take + specific statistic
X/Twitter
Post: Your remote team's “active hours” dashboard is measuring the wrong thing.
23% less output from the teams with the highest activity scores, in our audit of 40 companies.
Activity ≠ output. Full breakdown: [LINK]
Built from: same activity-tracking statistic, condensed for a single scroll-stopping claim
Hook type: specific number stated as a direct claim
Instagram Caption
Post: Plot twist: the remote employees who look the busiest on paper are often shipping the least. 👀
We pulled data from 40 remote teams and found the ones obsessed with “active hours” actually produced 23% less than teams that just tracked what got finished each week.
Busy looks like work. It isn't always work.
Full story linked in bio 🔗
Built from: the same core finding, reframed as a visual/emotional hook for a scroll-and-skim audience
Hook type: curiosity gap (“plot twist”) + relatable observation
Content repurposing usually fails for a boring reason: the post gets shortened, not reframed. A paragraph that works in a 1,500-word article because the reader is already three sections deep and invested doesn't work as a cold open, because a scrolling stranger has none of that context and none of that investment. This prompt is built around a single idea: each platform needs a different entry point into the same underlying material, not a shorter version of the same entry point.
Why the hook-type labeling matters
The instruction to vary hook types — and to explicitly label which one each post uses — exists because AI models left unconstrained default to the same opening pattern over and over, usually a rhetorical question (“Did you know...?”) or a bland statistic lead-in. A set of three posts that all open with a question isn't three distinct pieces of content; it's the same post copied three times with different fonts. Forcing an explicit, named hook type per post — contrarian take, curiosity gap, specific number — is what actually produces platform-appropriate variety instead of repetition.
Why the “Built from” attribution is there
Tracing each post back to a specific section of the source does two things. First, it makes fabrication harder to sneak past review — if a post claims a statistic, the writer or editor can immediately check it against the labeled source section rather than the whole article. Second, it prevents the common failure mode where all the generated posts accidentally cluster around the same one or two ideas from the source, leaving the rest of the article's substance unused. Seeing the attribution laid out makes that clustering visible immediately, before the posts go out.
Why the brand voice conflict flag matters
Most repurposing prompts assume the source content and the desired social voice are already aligned. They often aren't — a technical blog post written in a formal register doesn't automatically translate into a brand's “direct and irreverent” social voice without some genuine tension between accuracy and tone. Asking the model to flag that conflict, rather than silently resolving it by picking one side, keeps a human in the loop on the one decision that actually requires judgment: whether it's acceptable to loosen the tone or whether the technical accuracy needs to win.
Where this earns its keep
This is most useful for teams publishing long-form content regularly and syndicating it across 2-4 social channels, especially where the same person is responsible for both the writing and the distribution and doesn't have time to manually reframe the piece for each platform's actual reading behavior.