content-repurposer
Skill0 starsChanged 7 months agoMITView on GitHub
Адаптация одного контента под 5+ платформ. Один текст → Telegram, Instagram, Threads/X, LinkedIn, Reels скрипт. Активируется на: repurpose, адаптируй, переделай под, из одного поста, мультиплатформа, контент для платформ, один пост в 5.
We split this skill into the rules it gives an agent
19 rules. 0 are common, 19 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
No copy-paste rewording. Each version is native to its platform: different hooks, different structure, different length, different CTA.
- Distinctive: line 55
Before adapting, extract from the source:
- Distinctive: line 69
Follow the platform rules below.
- Distinctive: line 83
Start with a bold hook line (question, controversial take, or number)
- Distinctive: line 84
Use short paragraphs (2–3 sentences max)
- Distinctive: line 85
Add emoji as bullet markers (not decoration)
- Distinctive: line 106
Goal: Stop the scroll, get saves and shares.
- Distinctive: line 109
Use line breaks aggressively (mobile readability)
- Distinctive: line 112
Add 5–15 hashtags at the end (mix of big + niche)
- Distinctive: line 136
Write text that works WITHOUT images (user adds visuals later)
- Distinctive: line 159
No hashtags on Threads. 1–2 hashtags on X max.
- Distinctive: line 161
Use "🧵" marker on first post if thread
- Distinctive: line 179
Write as spoken word (not text style)
- Distinctive: line 209
Use "I" statements and professional storytelling
- Distinctive: line 210
Add a lesson or framework (LinkedIn loves teachable moments)
- Distinctive: line 232
Always structure your response like this:
- Distinctive: line 281
If input is mixed — use the dominant language
- Distinctive: line 326
Ask for specific platforms: if you don't need all 6 — saves time and focus.
- Distinctive: line 328
Chain with other skills: Use after writing a blog post, recording a podcast, or preparing a talk.
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Repurposer
One content → 5 platforms → 10 minutes saved per post.
You receive ONE piece of content — a post, article, idea, voice memo transcript, or URL — and transform it into ready-to-publish versions for every major platform.
No copy-paste rewording. Each version is native to its platform: different hooks, different structure, different length, different CTA.
Quick Start
repurpose: [paste your text or idea]адаптируй под все платформы: [текст]repurpose this for Telegram + Reels: [text]What You Produce
From ONE input, output ALL of these (unless user specifies platforms):
| # | Platform | Format | Length |
| 1 | Telegram | Long-form post | 800–2000 chars |
| 2 | Instagram caption | Story-driven + hashtags | 500–1500 chars |
| 3 | Instagram carousel | Slide-by-slide text (8–12 slides) | 50–120 chars/slide |
| 4 | Threads / X | Thread of 3–5 punchy posts | 200–500 chars each |
| 5 | Reels / Shorts script | Hook → Content → CTA with timecodes | 30–90 sec |
| 6 | Professional insight post | 600–1500 chars |
Workflow
Step 1 — Extract the Core
Before adapting, extract from the source:
CORE MESSAGE: [One sentence — what is the key idea?]
TARGET AUDIENCE: [Who cares about this?]
EMOTIONAL HOOK: [What feeling does this trigger?]
PROOF/STORY: [What evidence or story supports it?]
DESIRED ACTION: [What should the reader do after?]Show this extraction to the user as "🧠 Core Message Map" before the outputs.
Step 2 — Adapt Per Platform
Follow the platform rules below. Each output must feel like it was written natively for that platform, not "reformatted."
Step 3 — Deliver
Format output as clearly separated blocks with headers. Each block is copy-paste ready.
Platform Rules
📱 Telegram
Goal: Deep value, trust, direct link.
- Start with a bold hook line (question, controversial take, or number)
- Use short paragraphs (2–3 sentences max)
- Add emoji as bullet markers (not decoration)
- End with a soft CTA (question to comments, or "save this")
- No hashtags. Telegram doesn't use them
- Formatting: bold for key phrases,
—for dashes, line breaks between paragraphs - Tone: conversational, like texting a smart friend
Structure:
🔥 Hook (1 line)
Context / Problem (2-3 short paragraphs)
Key insight / Solution
💡 Takeaway or list of points
CTA (question or save prompt)📸 Instagram Caption
Goal: Stop the scroll, get saves and shares.
- First line = scroll-stopping hook (appears before "more")
- Use line breaks aggressively (mobile readability)
- Include a micro-story or personal angle
- End with a CTA question (drives comments = algorithm boost)
- Add 5–15 hashtags at the end (mix of big + niche)
- Tone: personal, relatable, slightly emotional
Structure:
[HOOK — first 125 chars are critical, this shows in preview]
[Story / Value — 3-5 short paragraphs]
[CTA — question to audience]
.
.
.
#hashtag1 #hashtag2 ... (5-15 relevant hashtags)🎠 Instagram Carousel
Goal: Saves, shares, educational value.
- Slide 1 (Cover): Bold statement or question. This IS the hook.
- Slides 2–10: One idea per slide. Max 3 lines of text per slide.
- Last slide: CTA — save, share, follow, comment.
- Write text that works WITHOUT images (user adds visuals later)
- Number each slide
- Tone: punchy, authoritative, clear
Format:
SLIDE 1 (Cover): [Bold hook / title]
SLIDE 2: [Problem or context]
SLIDE 3: [Point 1]
SLIDE 4: [Point 2]
SLIDE 5: [Point 3]
...
SLIDE N (Final): [CTA + summary]🧵 Threads / X
Goal: Virality, reposts, discussion.
- Post 1: Hot take or counterintuitive claim (this must stand alone)
- Posts 2–4: Supporting points, each self-contained
- Last post: Conclusion + CTA (repost/follow)
- Each post: 200–500 chars max
- No hashtags on Threads. 1–2 hashtags on X max.
- Tone: sharp, opinionated, zero fluff
- Use "🧵" marker on first post if thread
Format:
POST 1: 🧵 [Hot take / bold claim]
POST 2: [Supporting evidence / story]
POST 3: [Practical takeaway]
POST 4: [CTA — agree? repost / follow for more]🎬 Reels / Shorts Script
Goal: Watch time, follows, funnel entry.
- 0–3 sec: HOOK — visual + text hook that stops scrolling
- 3–15 sec: CONTEXT — set up the problem
- 15–45 sec: VALUE — deliver the insight/solution
- 45–60 sec: CTA — follow, comment, link in bio
- Write as spoken word (not text style)
- Include [VISUAL NOTES] for what to show on screen
- Tone: energetic, direct, like talking to a friend
Format:
[0:00–0:03] HOOK
Text on screen: "[HOOK TEXT]"
Say: "[SPOKEN HOOK]"
[Visual: describe what viewer sees]
[0:03–0:15] SETUP
Say: "[CONTEXT]"
[Visual: ...]
[0:15–0:45] VALUE
Say: "[MAIN CONTENT]"
[Visual: ...]
[0:45–0:60] CTA
Say: "[CALL TO ACTION]"
Text on screen: "[CTA TEXT]"Goal: Professional authority, network growth.
- First line = hook (shows in preview before "see more")
- Short paragraphs (1–2 sentences)
- Use "I" statements and professional storytelling
- Add a lesson or framework (LinkedIn loves teachable moments)
- End with a question (drives comments)
- No hashtags in body. 3–5 hashtags at the very end
- Tone: thoughtful, professional but human, slightly vulnerable
Structure:
[Hook line — provocative or personal]
[Story / Context — 3-4 short paragraphs]
[Insight / Framework / Lesson]
[CTA question]
#hashtag1 #hashtag2 #hashtag3Output Format
Always structure your response like this:
🧠 CORE MESSAGE MAP
━━━━━━━━━━━━━━━━━━
Core message: ...
Audience: ...
Hook: ...
Proof: ...
Action: ...
━━━━━━━━━━━━━━━━━━
📱 TELEGRAM
━━━━━━━━━━━━━━━━━━
[Ready-to-copy post]
━━━━━━━━━━━━━━━━━━
📸 INSTAGRAM CAPTION
━━━━━━━━━━━━━━━━━━
[Ready-to-copy caption]
━━━━━━━━━━━━━━━━━━
🎠 INSTAGRAM CAROUSEL
━━━━━━━━━━━━━━━━━━
[Slide-by-slide text]
━━━━━━━━━━━━━━━━━━
🧵 THREADS / X
━━━━━━━━━━━━━━━━━━
[Thread posts]
━━━━━━━━━━━━━━━━━━
🎬 REELS / SHORTS SCRIPT
━━━━━━━━━━━━━━━━━━
[Timed script with visual notes]
━━━━━━━━━━━━━━━━━━
💼 LINKEDIN
━━━━━━━━━━━━━━━━━━
[Ready-to-copy post]Adaptation Rules
Language
- Detect input language automatically
- Output in the SAME language as input
- If input is mixed — use the dominant language
Tone Matching
- Analyze the voice of the original: formal/casual, serious/playful, expert/peer
- Preserve the author's voice across all platforms
- Adapt FORMALITY per platform, but keep the personality
Content That Works Better on Some Platforms
- Data/numbers → prioritize Carousel + LinkedIn
- Personal story → prioritize Instagram caption + Reels
- Hot take/opinion → prioritize Threads + Reels hook
- Tutorial/how-to → prioritize Carousel + Reels + Telegram
- Inspiration → prioritize Instagram caption + LinkedIn
Commands
| Command | Action |
repurpose: [text] | Full 6-platform output |
repurpose for [platform]: [text] | Specific platform(s) only |
repurpose from URL: [url] | Extract content from URL, then repurpose |
adapt tone: [casual/expert/provocative] | Override detected tone |
add CTA: [specific CTA] | Use custom call-to-action across all |
focus: [carousel/reels/threads] | Expanded output for selected format |
Anti-patterns
- ❌ Don't just shorten the same text for each platform — rewrite natively
- ❌ Don't use hashtags on Telegram or Threads
- ❌ Don't write Reels scripts like blog posts — use spoken language
- ❌ Don't make LinkedIn sound like Instagram — different audience, different tone
- ❌ Don't skip the Core Message Map — it ensures consistency across platforms
- ❌ Don't produce walls of text — every platform has its own density
- ❌ Don't add generic hashtags — each must be relevant to the content
Pro Tips
- Best input = detailed text. The more context you give, the sharper the output.
- Voice memos work great. Paste the transcript — natural speech makes better content.
- Ask for specific platforms if you don't need all 6 — saves time and focus.
- Iterate: "make the Threads version more provocative" or "shorter Telegram version" — just ask.
- Chain with other skills: Use after writing a blog post, recording a podcast, or preparing a talk.
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- irinabuht12-oss/marketing-skills★ 5.6ksame name
- Affitor/affiliate-skills★ 709same name
- OneWave-AI/claude-skills★ 378same name
- Ootto-AI/claude-content-skills★ 280same name
- hamzafarooq/claude-code-starter★ 145same name
- aircrushin/promptMinder★ 113same name
- travisjneuman/.claude★ 106same name
- marcosmodly/marketing-skill★ 36same name
- OpenAnalystInc/10x-Content-Expert★ 15same name
- legioncodeinc/littlebird-skills★ 8same name
19 more not listed
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.
Used alongsideProjects with it also use landing-page-copywriter, research-synthesizer and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
julianromliSkilllanding-page-copywriter
Write high-converting landing page copy using proven frameworks like PAS (Problem-Agitate-Solution), AIDA, and StoryBrand. Creates headlines, value propositions, CTAs, and full page sections optimized for conversion. Use when users need landing page copy, sales page content, or marketing website text.
Also in 4 projects that use this
o2alexanderfedinSkillresearch-synthesizer
Creates comprehensive synthesis documents distilling research findings into actionable insights. Activates when: creating synthesis.md files, aggregating research findings, integrating multi-source data, extracting strategic insights, or resolving conflicting information. Operates across technical, market, architecture, certification, and roadmap domains. Ensures evidence-based synthesis with full traceability to source research files.
Also in 3 projects that use this
vivy-yiSkillcontent-calendar
Use when scheduling Xiaohongshu posts, maintaining consistent posting frequency, planning content around events or seasons, or organizing content production workflow
Also in 4 projects that use this
ncklrsSkillproposal-writer
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
Also in 4 projects that use this
In this repository35 other files it gives its agents.
- agent-architectSkill
- agent-memorySkill
- audience-lensSkill
- carouselSkill
- constructor-opsSkill
- copywritingSkill
- customer-researchSkill
- editingSkill
- headlinesSkill
- heygenSkill
- learning-processorSkill
- memory-systemSkill
- nano-banana-pro-promptsSkill
- nano-bananaSkill
- openclaw-opsSkill
- personal-unpackingSkill
- prompt-engineerSkill
- reelsSkill
- selling-meaningsSkill
- seo-blog-writerSkill
- shared-learningsSkill
- skill-creatorSkill
- skill-securitySkill
- soul-masterySkill
- storytellingSkill
- swipefileSkill
- telegram-adminSkill
- telegramSkill
- text-postsSkill
- threadsSkill
- timelapse-creatorSkill
- tone-of-voiceSkill
- veo-videoSkill
- video-editorSkill
- youtubeSkill
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.

