AgriciDaniel/claude-repurpose / skills/repurpose
repurpose
VerifiedContent Repurposing Engine. Transforms any content (YouTube videos, blog posts, podcasts, local files, pasted text) into platform-optimized outputs for Twitter/X, Threads, LinkedIn, Instagram, TikTok, Pinterest, Snapchat, Facebook, YouTube Community, Skool, Discord, Reddit, Quora, Medium, WhatsApp Channels, Telegram, and email newsletters. Atomizes content into reusable pieces, adapts brand voice per platform, generates polls, image prompts (via /banana), publishing calendars, and SEO metadata. Triggers on: "repurpose", "content repurpose", "turn into social media", "cross-platform", "content atomization", "repurpose blog", "repurpose video", "turn this into posts", "threads", "pinterest", "snapchat", "discord", "medium", "whatsapp", "telegram".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.8 KB |
| references/engagement-benchmarks.md | markdown | 7.2 KB |
| references/hook-formulas.md | markdown | 9.5 KB |
| references/image-sourcing.md | markdown | 7.0 KB |
| references/mistakes-to-avoid.md | markdown | 4.0 KB |
| references/platform-specs.md | markdown | 7.3 KB |
| references/poll-strategy.md | markdown | 4.2 KB |
| references/repurposing-frameworks.md | markdown | 8.1 KB |
| references/voice-adaptation.md | markdown | 8.5 KB |
references/mistakes-to-avoid.md
View on GitHub# Top 10 Content Repurposing Mistakes
Common failures in content repurposing and how this skill prevents each one.
## 1. Copy-Pasting the Same Text Across Platforms
**Why it fails:** Each platform has distinct norms, attention spans, and audience expectations. A LinkedIn post reads nothing like a tweet. Cross-posting identical text signals laziness and gets suppressed by algorithms tuned for native content.
**How we prevent it:** Sub-skills enforce platform-specific formatting, tone, length, and structure. Every output is rewritten for its target platform, not reformatted.
## 2. External Links in the Main Post Body
**Why it fails:** Twitter gives near-zero reach to link posts for non-Premium accounts. LinkedIn suppresses posts with links by ~40%. Algorithms want users to stay on-platform.
**How we prevent it:** Links go in the first comment (LinkedIn), bio reference (Twitter), or swipe-up/link sticker (Stories). The main post body never contains an external URL.
## 3. Over-Hashtagging
**Why it fails:** Diminishing returns hit fast. More hashtags does not mean more reach; it signals spam.
- Instagram: 3-5 maximum
- Twitter/X: 0-2 maximum
- LinkedIn: 3-5 maximum
**How we prevent it:** platform-specs.md enforces hard limits per platform. Hashtags are curated for relevance, not volume.
## 4. Posting Everything on the Same Day
**Why it fails:** Audience fatigue. Algorithms do not reward flood posting. Followers see multiple similar posts and tune out. You also burn all your content in one day with no follow-up.
**How we prevent it:** The calendar sub-skill staggers posts across 5-7 days, sequencing formats for maximum sustained visibility.
## 5. Ignoring Mobile-First Formatting
**Why it fails:** 75%+ of social media is consumed on mobile. Dense paragraphs, long unbroken lines, and buried key points get scrolled past instantly.
**How we prevent it:** All outputs use short paragraphs (1-2 sentences max), deliberate line breaks, and front-loaded key information. The hook is always in the first line.
## 6. Generic Hooks ("Here's what I learned...")
**Why it fails:** Hook fatigue is real in 2026. Audiences have been trained to scroll past formulaic openers. "I just realized something..." and "Here's what nobody tells you..." are invisible now.
**How we prevent it:** hook-formulas.md requires specific, curiosity-driven, platform-native hooks. Every hook is checked against a staleness filter. Specificity beats formula.
## 7. Ignoring the Reply/Comment Strategy
**Why it fails:** On Twitter, a reply is worth 27x a like. On LinkedIn, comments over 10 words signal quality engagement. Posting without a plan for the conversation is leaving reach on the table.
**How we prevent it:** Every output includes engagement prompts, suggested reply angles, and a comment strategy. The first comment is pre-written where applicable (LinkedIn, YouTube).
## 8. Wrong Image Aspect Ratios Per Platform
**Why it fails:** Images get cropped awkwardly, text gets cut off, or the image displays with letterboxing. Each platform has specific display dimensions and cropping behavior.
**How we prevent it:** platform-specs.md specifies exact dimensions per format. image-sourcing.md enforces correct aspect ratios via the 3-tier pipeline.
## 9. Publishing Without a Human Editing Pass
**Why it fails:** AI-generated content has a detectable voice. Brand voice inconsistency erodes trust. Factual errors, outdated references, or tone-deaf phrasing slip through without human review.
**How we prevent it:** summary.md flags items requiring human review. voice-adaptation.md preserves brand tone. The skill explicitly marks content as "draft for review," not "ready to publish."
## 10. Skipping Polls
**Why it fails:** Polls are the highest-engagement format on LinkedIn (8.9%) and a top performer on YouTube Community. They are trivial to create from existing content yet consistently overlooked.
**How we prevent it:** Every platform output includes a poll derived from the source content. poll-strategy.md provides the framework for transforming any content into a genuine, engagement-driving poll.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |