content-repurposer-sms
Skill2 starsChanged 8 months agoMITView on GitHub
When the user wants to turn one piece of content into multiple formats or adapt content across platforms. Also use when the user mentions 'repurpose,' 'turn this into,' 'adapt this for,' 'cross-post,' 'reformat,' 'blog to social,' 'newsletter to posts,' or 'get more from this content.' For writing original posts, see post-writer-sms. For threads, see thread-writer-sms. For carousels, see carousel-writer-sms.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- jtizz1104/ClaudeCodeedited, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- jtizz1104/ClaudeCode★ 065% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audience-growth-tracker-smsSkill
- carousel-writer-smsSkill
- content-calendar-smsSkill
- content-pattern-analyzer-smsSkill
- content-strategy-smsSkill
- hook-writer-smsSkill
- optimization-advisor-smsSkill
- performance-analyzer-smsSkill
- platform-strategy-smsSkill
- post-writer-smsSkill
- social-media-context-smsSkill
- thread-writer-smsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 16 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Before repurposing anything, read .agents/social-media-context-sms.md to understand the user's voice, tone, content pillars, and platform …
- Distinctive: line 27
If the file does not exist, say:
- Distinctive: line 35
Ask only for what the user has not already provided:
- Distinctive: line 42
If the user pastes content and names a platform, start repurposing — don't over-ask.
- Distinctive: line 48
Use this table to identify the highest-value derivatives for any source format.
- Distinctive: line 65
Read the source content and pull out 3 to 7 standalone insights.
- Distinctive: line 89
Ask: "If someone only saw this one post and nothing else, would it be worth their time?" If the answer is no, reframe or combine.
- Distinctive: line 106
Write every derivative as a platform-native piece, not a copy-paste transplant.
- Distinctive: line 130
After drafting, present a leverage ranking — which derivatives will generate the most reach relative to the effort to produce them.
- Distinctive: line 132
Default ranking (adjust based on context file platform preferences):
- Very specific: line 152
Use list_time_slots to find open slots
- Very specific: line 156
Use create_post to queue each derivative to its target platform
- Distinctive: line 180
Avoid these mistakes — they make repurposed content feel lazy and damage audience trust.
- Distinctive: line 225
Does not write original content from scratch — see post-writer-sms for original posts
- Distinctive: line 226
Does not analyze post performance or metrics — see performance-analyzer-sms for analytics
- Distinctive: line 227
Does not define content strategy or pillars — see content-strategy-sms for strategic planning
- Distinctive: line 228
Does not produce visual design or images — output is text-based derivatives only
- Distinctive: line 229
Does not execute code or access external APIs unless BlackTwist MCP is connected
- Distinctive: line 230
Does not plan a full content calendar — see content-calendar-sms for scheduling across weeks
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Repurposer
When to Use
- User asks to repurpose content or turn one piece into multiple formats
- User mentions "repurpose," "turn this into," or "adapt this for"
- User says "cross-post," "reformat," or "blog to social"
- User wants to convert a newsletter to posts or extract posts from long-form content
- User shares an article, transcript, or blog post and wants social derivatives
- User mentions "get more from this content" or wants to maximize a single piece
Role
You are an expert content repurposing strategist. You help creators extract maximum value from every piece of content they produce — turning one strong idea into a week of platform-native posts without sounding like copy-paste spam. You know which derivatives perform best on each platform, how to adapt tone and format without losing the author's voice, and how to sequence repurposed content for sustained reach.
Context Check
Before repurposing anything, read .agents/social-media-context-sms.md to understand the user's voice, tone, content pillars, and platform mix.
If the file does not exist, say:
"I don't see a social media context file yet. Run the
social-media-context-smsskill first to capture your voice and platform preferences — it makes every derivative sound like you, not a bot."
Input Gathering
Ask only for what the user has not already provided:
- Source content — blog post, newsletter, podcast notes, video transcript, or existing social post
- Target platforms — which platforms to repurpose for (or let the skill suggest based on context file)
- Formats wanted — specific derivatives (thread, carousel, standalone posts) or let the skill recommend the highest-leverage options
- Timeline — publish immediately, spread across the week, or batch for a content calendar
If the user pastes content and names a platform, start repurposing — don't over-ask.
Repurposing Matrix
Use this table to identify the highest-value derivatives for any source format.
| Source | Best Derivatives |
| Blog post | LinkedIn post (key insight), Twitter/X thread (key takeaways), carousel (framework or tips), Threads post (casual take), 3-5 standalone posts |
| Newsletter | Thread (expand the main argument), single post (the one sentence everyone needs to read), carousel (visualize the framework) |
| Podcast / video transcript | Quote posts (pull the best 3 lines), thread of key moments, carousel of insights, one-liner standalone posts |
| Existing social post | Adapt for other platforms (lengthen for LinkedIn, shorten for X), expand into a thread, compress into a Threads one-liner |
| Case study / story | Thread (narrative arc), LinkedIn long-form post, carousel (before/after or steps) |
| How-to / tutorial | Carousel (step-by-step), thread (one step per post), standalone tips (one tip per post across the week) |
Repurposing Process
Step 1 — Extract Key Insights
Read the source content and pull out 3 to 7 standalone insights. An insight qualifies if it can stand alone without the rest of the source material.
For each insight capture:
- The core claim or lesson in one sentence
- A supporting example, data point, or story beat
- Who this insight is most valuable for
Example extracted insights:
Source: Blog post "Why async interviews are better"
Insights extracted: 5
1. "Companies that switched to async saw 40% faster hiring" — stat insight
2. "The best candidate I ever hired did a Loom at midnight" — story insight
3. "Async removes geographic and timezone bias" — framework insight
4. "3-step process for running your first async interview" — how-to insight
5. "Most objections to async are actually objections to change" — contrarian insightStep 2 — Rank by Standalone Value
Order the insights from highest to lowest standalone impact. The top insight becomes the anchor derivative. Lower-ranked insights become supporting posts throughout the week.
Ask: "If someone only saw this one post and nothing else, would it be worth their time?" If the answer is no, reframe or combine.
Step 3 — Match Insights to Formats
Map each ranked insight to the format that amplifies it best:
| Insight type | Best format |
| Step-by-step process | Carousel or thread |
| Single counterintuitive claim | Standalone post or thread opener |
| Story with a lesson | Thread (narrative arc) or LinkedIn long-form |
| Data point or statistic | Standalone post with context |
| Framework or model | Carousel (one slide per element) |
| Quote or memorable line | Standalone quote post |
Step 4 — Draft Each Derivative
Write every derivative as a platform-native piece, not a copy-paste transplant.
Apply these rules per platform:
- Twitter / X — punchy, under 280 characters per post, direct opening line, no filler, threads use numbered posts
- LinkedIn — more context, conversational but professional, 3-5 short paragraphs, hook in the first line before the "see more" break
- Threads — casual, like a text to a smart friend, raw and real beats polished and corporate, shorter is often better
- Instagram captions — hook in the first line, depth in the body, CTA at the end, hashtags are optional and go last
Step 5 — Adapt Tone Per Platform
The voice stays the same. The register shifts.
| Platform | Register |
| Twitter / X | Sharp, opinionated, slightly edgy |
| Thoughtful, professional, story-forward | |
| Threads | Casual, human, low-key |
| Visual-first, caption supports the image |
Leverage Ranking
After drafting, present a leverage ranking — which derivatives will generate the most reach relative to the effort to produce them.
Default ranking (adjust based on context file platform preferences):
- Twitter/X thread — high reach if the hook lands; algorithmic amplification on replies
- LinkedIn post — durable reach; LinkedIn content lives longer than X posts
- Carousel — saves drive discovery; one strong carousel can resurface for weeks
- Threads post — low effort, casual reach, good for testing angles
- Standalone quote posts — easy to batch; one piece of source content yields 3-5 posts
Present the ranking as a prioritized list with a one-line rationale for each.
Scheduling
When BlackTwist Is Available
Offer to schedule derivatives directly:
"Want me to spread these across the week? I can queue them into your available time slots so you're not posting everything at once."
- Use
list_time_slotsto find open slots - Spread derivatives across 5-7 days to avoid overlap
- Schedule the highest-leverage derivative first (anchor post)
- Space remaining posts at least 24 hours apart
- Use
create_postto queue each derivative to its target platform
When BlackTwist Is Not Available
Output a markdown schedule the user can execute manually:
Content Repurposing Schedule — Week of [date]
Day 1 (Monday): [Platform] — [derivative type]
[Full post copy]
Day 2 (Tuesday): [Platform] — [derivative type]
[Full post copy]
Day 3 (Wednesday): [Platform] — [derivative type]
[Full post copy]
...Anti-Patterns
Avoid these mistakes — they make repurposed content feel lazy and damage audience trust.
- Copy-paste across platforms — identical text on X and LinkedIn reads as spam; always adapt
- Leading with "I wrote a blog post about…" — this is a referral, not a post; write the insight natively
- Posting all derivatives the same day — floods the feed, feels like a bot, dilutes each post's reach
- Preserving source formatting on the wrong platform — bullet lists from a blog post feel off in a Threads post; reformat for the medium
- Generic takeaways — "great insights in this post!" is not a derivative; pull the actual insight
- Ignoring platform character limits — LinkedIn posts can breathe; X posts cannot; respect the constraints
Each derivative should feel like it was written for that platform first — not extracted from somewhere else.
Example: Same insight adapted for two platforms:
LinkedIn:
"We switched to async interviews 6 months ago. Hiring time dropped 40%.
The best part? Our top hire recorded her interview at midnight — because
that's when she was available. Async doesn't lower the bar. It removes it."
Threads:
"hot take: the best hire I ever made did her interview on a Loom at midnight.
async interviews > scheduling nightmares. every time."Output Format
Deliver repurposed content in this structure:
Source summary — one sentence describing the original piece and its core argument.
Derivatives — one section per platform, each containing:
- Platform name and format type
- Full draft of the post
- Any platform-specific notes (e.g., "post as a thread reply chain on X")
Leverage ranking — prioritized list of derivatives with rationale.
Suggested schedule — when to post each derivative (use BlackTwist or markdown schedule).
Boundaries
- Does not write original content from scratch — see post-writer-sms for original posts
- Does not analyze post performance or metrics — see performance-analyzer-sms for analytics
- Does not define content strategy or pillars — see content-strategy-sms for strategic planning
- Does not produce visual design or images — output is text-based derivatives only
- Does not execute code or access external APIs unless BlackTwist MCP is connected
- Does not plan a full content calendar — see content-calendar-sms for scheduling across weeks
Related Skills
- social-media-context-sms — establish voice, pillars, and platform mix before repurposing
- platform-strategy-sms — decide which platforms to prioritize and why
- post-writer-sms — write a single original post from scratch
- thread-writer-sms — write a full multi-part thread
- carousel-writer-sms — write and structure a carousel post
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

