Skip to content

AgriciDaniel/claude-repurpose / skills/repurpose

repurpose

Verified

Content 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".

references/repurposing-frameworks.md

View on GitHub
# Repurposing Frameworks

Four actionable frameworks for content atomization, scheduling, and maximizing reach. Apply these during the atomization step and calendar generation.

---

## Framework 1: One Pillar, Many Cuts (Gary Vee Model)

Start with one pillar content piece and extract dozens of micro-content moments.

**Process:**

1. **Create or identify the pillar** — one long-form piece (video, article, podcast episode, webinar, keynote)
2. **Extract 30-50 micro-content moments** from the pillar:
   - Quotable one-liners
   - Individual tips or steps
   - Stories or anecdotes
   - Data points and statistics
   - Controversial or contrarian takes
   - Before/after moments
   - Questions asked or answered
3. **Format each moment for its target platform** — same idea, different packaging
4. **Schedule across days and weeks** — never dump everything at once

**Real-world results:** Gary Vee's team turns one 60-minute keynote into 35M+ total views across micro-content pieces. The pillar itself may get 500K views, but the derivatives collectively 70x that reach.

**When to apply:** This is the default framework for any pillar content longer than 10 minutes (video/audio) or 1,500 words (text). Use it whenever the user provides a substantial piece of content.

**Atomization rule:** Extract more atoms than you think you need. You can always discard low-impact ones, but you cannot create atoms that were not in the original content.

---

## Framework 2: Content Atomization (Hub-and-Spoke)

One "Big Rock" asset serves as the hub. Every derivative is a spoke pointing back to the hub.

**Structure:**

```
                    [Blog Post]
                    [Newsletter]
                   /            \
          [Thread]    [BIG ROCK]    [Carousel]
                   \            /
                    [Quote Cards]
                    [Reel Script]
                    [Community Poll]
```

**Atom categories (extract 5-15):**

| Atom Type | Description | Standalone Value |
|-----------|-------------|-----------------|
| `stat` | A specific number or data point | High — works as tweet, slide, or quote card |
| `quote` | A memorable phrase or sentence | High — works everywhere |
| `insight` | A non-obvious takeaway | Medium-High — needs 1-2 sentences of context |
| `question` | A thought-provoking question | High — drives comments on any platform |
| `contrarian` | A bold or counterintuitive claim | Very High — highest engagement potential |
| `howto` | An actionable step or instruction | Medium — best in threads, carousels, newsletters |
| `analogy` | A comparison or metaphor | Medium — great for making complex ideas click |
| `casestudy` | A real example or result | High — credibility builder on all platforms |
| `prediction` | A forward-looking claim | Medium-High — drives debate and saves |

**Expected result:** One Big Rock asset produces 2-3x audience reach and content ROI compared to creating individual pieces from scratch.

**Atomization instruction:** When extracting atoms, label each with its type and rate its standalone impact from 1-5:
- **5** — Works perfectly as a standalone post on any platform
- **4** — Works standalone with minor context
- **3** — Needs a sentence of setup but strong payoff
- **2** — Supporting material; best paired with another atom
- **1** — Context-dependent; use only in longer formats (thread, carousel, newsletter)

---

## Framework 3: Content Waterfall (Weekly Cascade)

A structured weekly schedule that cascades one piece of content across platforms over 7 days.

**Weekly schedule:**

| Day | Platform | Format | Content Focus |
|-----|----------|--------|---------------|
| **Monday** | Blog / Newsletter | Long-form article | Full pillar content published |
| **Tuesday** | Twitter + LinkedIn | Thread + Carousel | Key insights extracted as visual/text formats |
| **Wednesday** | Instagram + All platforms | Quote cards + Visual posts | Best quotes and stats as designed images |
| **Thursday** | All platforms | Polls | Turn insights into interactive questions |
| **Friday** | Email list | Newsletter send | Curated excerpt with exclusive angle |
| **Saturday** | YouTube Community + Skool | Community posts | Behind-the-scenes, discussion, challenges |
| **Sunday** | Facebook + Skool | Stories + Light engagement | Questions, casual reflections, community building |

**Compounding effect:** One thread + its derivatives = 14 distinct pieces of content over 6 weeks when you factor in reshares, quote tweets, and evergreen recycling.

**Scheduling rules:**
- Never post the same content on two platforms the same day
- Space out high-effort formats (thread, carousel, newsletter) across the week
- Polls go on Thursday because mid-week engagement peaks
- Weekend content should be lighter, more personal, community-focused
- Each day's content should be self-contained (someone who missed Monday can still engage with Thursday's poll)

---

## Framework 4: 8-Step Repurposing System

A comprehensive system for teams or creators who want to build a sustainable repurposing practice.

### Step 1: Audit and Inventory
- Catalog all existing content (blog posts, videos, podcasts, newsletters, social posts)
- Tag by topic, format, date, and performance
- Identify gaps in your content library

### Step 2: Identify High-Performers
- Sort existing content by traffic, engagement, and conversions
- Top 20% of content = your repurposing goldmine
- Prioritize evergreen content over timely/news pieces
- Look for content that performed well on one platform but was never adapted for others

### Step 3: Map Content Types to Platform Formats
- Match each content type to the platform formats where it performs best:
  - Data-heavy content → Twitter threads, LinkedIn carousels, newsletter deep-dives
  - Story-driven content → Instagram carousels, Facebook posts, YouTube Community
  - Opinion/contrarian content → Twitter standalone, LinkedIn text posts, Reddit
  - How-to content → Threads, carousels, email sequences, Skool challenges
  - Case studies → LinkedIn posts, newsletter features, Reddit posts

### Step 4: Create a Message Map
For each piece of content, extract:
- **1 main claim** (the core thesis or takeaway)
- **3 supporting points** (the evidence or arguments)
- **3 proof items** (stats, examples, case studies, or quotes)
- This 1-3-3 structure maps directly to: tweet (claim), thread (claim + points), carousel (all), newsletter (all + depth)

### Step 5: Plan Distribution Alongside Creation
- Never create content without a distribution plan
- Before writing, decide: which 3-5 platforms will this reach?
- Build repurposing into the content creation process, not as an afterthought
- Create a shared calendar that shows creation dates AND distribution dates

### Step 6: Use AI as Accelerator
- AI handles the format adaptation (long-form → tweet, article → carousel copy)
- Human handles the voice, nuance, and final approval
- AI should never replace the original insight — only repackage it
- Review every AI output for accuracy, tone, and platform appropriateness

### Step 7: Track Performance to Close the Feedback Loop
- Monitor which atoms perform best on which platforms
- Feed performance data back into the atomization process
- Double down on atom types that consistently outperform
- Build a "best atoms" library from past content

### Step 8: Refresh Evergreen Content
- Every 3-6 months, revisit top-performing content
- Update statistics and examples with current data
- Re-repurpose with fresh formatting and hooks
- Evergreen content repurposed with updated data outperforms new content 60% of the time

---

## Choosing a Framework

| Scenario | Recommended Framework |
|----------|-----------------------|
| Single long-form piece, full repurpose | Framework 1 (One Pillar, Many Cuts) |
| Building a weekly content system | Framework 3 (Content Waterfall) |
| First time repurposing, need structure | Framework 4 (8-Step System) |
| Quick atomization for immediate posts | Framework 2 (Hub-and-Spoke) |
| Content audit + strategic planning | Framework 4, Steps 1-3 |
| Ongoing content program | Combine Framework 3 (schedule) + Framework 2 (atomization) |
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall