rampstackco/claude-skills / skills/content-repurposing
content-repurposing
VerifiedCross-format content adaptation. Turning one substantial piece into many derivative formats (blog series, email sequences, social posts, webinars, podcasts, video shorts) without losing the original's value or producing AI-slop variants. The discipline of adaptation per medium rather than mass-blast distribution. Triggers on content repurposing, content adaptation, cross-format content, content atomization, content multiplication, content distribution across formats, source-piece-to-derivative, video shorts from blog, email from whitepaper, podcast from article, blog series from research. Also triggers when a flagship piece is shipping but the team has not planned how to extend it across formats, when repurposing is happening but the derivatives feel mass-produced, or when AI-assisted repurposing is producing slop variants of strong source pieces.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 360 B |
| SKILL.md | skill md | 23.7 KB |
| references/aeo-extraction-patterns.md | markdown | 10.4 KB |
| references/common-repurposing-failures.md | markdown | 10.5 KB |
| references/cross-promotion-patterns.md | markdown | 9.5 KB |
| references/format-adaptation-patterns.md | markdown | 13.4 KB |
| references/per-format-constraints.md | markdown | 10.5 KB |
| references/repurposing-pipeline-templates.md | markdown | 11.4 KB |
| references/sequencing-and-cadence-patterns.md | markdown | 11.2 KB |
| references/source-piece-selection-criteria.md | markdown | 10.9 KB |
| references/voice-consistency-across-formats.md | markdown | 10.7 KB |
references/repurposing-pipeline-templates.md
View on GitHub# Repurposing pipeline templates
Workflow templates by source-piece type. Whitepaper pipeline, blog post pipeline, research report pipeline, multi-piece consolidation pipeline. The repeatable shapes that turn ad-hoc repurposing into a predictable program.
Repurposing without templates produces ad-hoc workflows: each cross-format extension is invented from scratch, capacity estimates are unreliable, quality varies. Templates make repurposing a known production shape, with predictable capacity and predictable quality.
The templates below are recurring shapes; teams adapt them to specific source pieces and program contexts.
---
## Pipeline 1: Whitepaper
**Source.** A 4,000-8,000 word whitepaper or definitive guide.
**Cross-format set (typical).**
- 4-6 blog posts (one per major section).
- 5-7 email sequence.
- 1 webinar.
- 12-18 social posts across LinkedIn, X, possibly Instagram or Threads.
- 6-12 video shorts.
- 10-15 FAQ extractions for AI search.
- Possibly 1 podcast episode.
**Production sequence.**
- Week 0: Source piece publishes.
- Week 1: First social posts ship; email teaser sends. FAQ extractions ship as part of the source piece (or as an immediately-following FAQ page).
- Weeks 2-6: Blog posts ship at 1-per-week cadence. Email sequence sends in parallel. More social posts ship from each blog post's release.
- Weeks 4-8: Webinar runs. Webinar recording becomes additional video derivatives.
- Weeks 6-10: Video shorts ship. Podcast episode (if applicable) records and releases.
**Capacity.** Typical whitepaper pipeline costs 30-60 hours of editorial and production work across 8-10 weeks, on top of the source piece's production cost.
**Owner structure.** Single owner-of-extensions for the whitepaper. Specific derivative owners by format (blog series owner, email sequence owner, social owner, video owner). The owner-of-extensions coordinates timing and ensures cross-promotion happens.
---
## Pipeline 2: Blog post (substantive)
**Source.** A 1,500-2,500 word substantive blog post on a multi-step framework or substantive topic.
**Cross-format set (typical).**
- 5-7 email sequence (if the source has a multi-step framework).
- 4-8 social posts.
- 2-4 video shorts.
- 3-5 FAQ extractions.
- Possibly 1 podcast episode segment (not full episode).
**Production sequence.**
- Week 0: Blog post publishes.
- Week 1: First social posts ship; email teaser if part of a sequence; FAQ extractions added to the post.
- Weeks 2-4: Email sequence sends. Additional social posts. Video shorts ship.
- Weeks 4-6: Long-tail social and AI-search-snippet refinement.
**Capacity.** Typical substantive blog post pipeline costs 8-15 hours of additional work across 4-6 weeks.
**Owner structure.** Often one owner runs the full extension for blog-post-tier sources because the work is small enough to coordinate in one head.
---
## Pipeline 3: Research report
**Source.** A 4,000-12,000 word research report with primary data.
**Cross-format set (typical).**
- 5-8 blog posts (one per major finding or section).
- 7-10 email sequence.
- 1-2 webinars (often a launch webinar plus a deeper-dive webinar).
- 20-30 social posts (research reports produce many statistic-driven social derivatives).
- 8-15 video shorts (statistic-focused).
- 15-25 FAQ extractions.
- 1-2 podcast episodes.
- Possibly an interactive data visualization or microsite.
**Production sequence.**
- Week -2 to Week 0: Pre-launch promotion teasers (research findings preview).
- Week 0: Source report publishes; launch webinar announces; first wave of statistic-focused social ships.
- Weeks 1-4: Heavy email sequence; blog posts ship; webinars run; social posts continue.
- Weeks 4-12: Video shorts roll out; podcast episodes record and release; FAQ extractions get refined as AI-search citations are tracked; second webinar runs for deeper-dive audience.
- Indefinitely: Statistics from the report continue to be cited in subsequent program pieces; the report becomes a reference asset.
**Capacity.** Research report pipelines are the highest-investment repurposing efforts. Typical cost: 60-150 hours of additional work across 8-16 weeks, on top of the report's production cost.
**Owner structure.** Owner-of-extensions plus dedicated derivative owners. Often a research report's cross-format extension is treated as a project with its own project manager rather than as a routine repurposing pipeline.
---
## Pipeline 4: Multi-piece consolidation (ebook)
**Source.** Multiple existing pieces (blog posts, articles, social threads) on a related topic.
**Cross-format set (typical).**
- 1 ebook (the primary consolidation).
- New introduction, chapter framings, conclusion within the ebook (often 20-30% new content).
- 4-7 promotional blog posts (potentially excerpting chapters or introducing the ebook).
- 5-8 email sequence promoting the ebook.
- 1 webinar based on the ebook's framework.
- 8-15 social posts promoting the ebook and its chapters.
- 3-6 video shorts.
**Production sequence.**
- Months 1-3: Source-piece selection and consolidation. Identify which existing pieces fit; outline the ebook; write new connective tissue; consolidate and edit for unified voice.
- Month 3-4: Production: design, layout, possibly PDF generation, gating setup if applicable.
- Month 4: Ebook launches. First promotional blog posts and emails ship. Webinar runs.
- Months 5-8: Promotional cadence continues. Video shorts and social posts roll out.
**Capacity.** Multi-piece consolidation pipelines often cost 60-120 hours of consolidation and production work, plus the standard derivative production. Total: 80-180 hours across 4-8 months.
**Owner structure.** A consolidation lead drives the editorial work; standard derivative owners run the promotional set. The consolidation lead often is a senior editor because the unified-voice editing is substantial.
---
## Pipeline 5: Trending topic editorial
**Source.** A 1,000-2,500 word editorial piece on a trending or news-driven topic.
**Cross-format set (typical, lighter than evergreen).**
- 4-7 social posts (concentrated in the first week to ride the trend).
- 1-2 video shorts.
- 1-2 FAQ extractions if the topic supports it.
- Often no email sequence (trending topics may not justify a multi-email investment).
- Often no webinar (production cycle is too long for trending topics).
**Production sequence.**
- Day 0: Source piece publishes.
- Days 1-7: Social posts ship rapidly to ride the trend. Video shorts ship if production cycle allows.
- Weeks 2-4: Long-tail social and AI-search-snippet refinement if the topic has staying power.
- After 4 weeks: Pipeline typically winds down as the trend fades.
**Capacity.** Trending topic pipelines are deliberately light: 4-10 hours of additional work across 1-2 weeks.
**Owner structure.** Often one owner runs the full extension because timeliness matters more than coordinated multi-format depth.
---
## Pipeline 6: Case study
**Source.** A 2,000-4,000 word case study with real specifics.
**Cross-format set (typical).**
- 3-5 blog posts pulling specific lessons or framework moments from the case.
- 3-5 email sequence (if the case study has clear teachable steps).
- 6-10 social posts (often statistic-driven from the case's outcomes).
- 1-3 video shorts (often featuring the case's customer if available, with their consent).
- 3-5 FAQ extractions.
- Possibly 1 webinar featuring the customer.
**Production sequence.**
- Week 0: Case study publishes.
- Week 1: First social posts ship; FAQ extractions added.
- Weeks 2-6: Blog posts and emails ship. Webinar runs (if part of the plan, often with customer participation).
- Weeks 4-10: Video shorts and additional social.
**Capacity.** Typical case study pipeline costs 15-30 hours of additional work, plus customer coordination time for any derivatives featuring the customer.
**Owner structure.** Customer-coordination owner plus standard derivative owners. The customer-coordination owner manages the relationship; derivative owners produce the work; the customer reviews customer-facing derivatives before they ship.
---
## Pipeline customization
Templates are starting points; programs adapt them.
**Customization based on audience.**
- B2B technical audiences: more LinkedIn, more whitepaper-driven; less TikTok and Instagram.
- Consumer audiences: more video and visual social; less long-form.
- Vertical-specific audiences: platform mix may differ (YouTube heavy in some industries; Twitter/X heavy in others).
**Customization based on capacity.**
- Smaller teams may execute Pipeline 1 with reduced scope (3 blog posts instead of 6, 6 social posts instead of 18).
- Larger teams may extend pipelines with additional derivatives the templates do not include (interactive tools, microsites, dedicated landing pages).
**Customization based on source characteristics.**
- Highly visual source pieces benefit from heavier video and visual-social investment.
- Voice-distinctive source pieces benefit from heavier email and podcast investment (where voice carries).
- Citation-rich source pieces benefit from heavier AEO-extraction investment.
---
## Pipeline tracking
Each pipeline run produces data that informs future pipelines.
**The minimum log per pipeline.**
- Source piece title, type, length, traffic at launch.
- Cross-format set planned vs delivered.
- Capacity spent (hours per derivative type).
- Outcomes per derivative (engagement, traffic, conversion, citation rates).
- Lessons learned (what worked, what failed, what to change next time).
**Pattern detection across pipelines.**
- Are some pipeline templates outperforming others on similar source types?
- Are some derivative types consistently outperforming others?
- Are capacity estimates accurate, or do certain pipelines consistently overrun?
- Are some channels consistently underperforming for the program's audience mix?
The log informs program-level decisions: which pipelines to invest in more deeply, which to drop, which to redesign.
---
## Common pipeline failures
**Pipeline-as-checklist.** The team treats the pipeline as a checklist to complete rather than as a coordinated plan. Each derivative gets produced; nothing connects to the others; cross-promotion is missing.
**Capacity underestimation.** Teams plan a Pipeline 1 expecting 30 hours; actual cost is 70 hours; new production suffers. Cure: track actual capacity per pipeline; calibrate estimates.
**Pipeline dogmatism.** Treating the template as a fixed shape regardless of source-piece characteristics. Some source pieces fit the template; some need customization. Cure: customize pipelines per source.
**No tracking.** Pipelines run; outcomes are not measured; the program does not learn. Cure: minimum log per pipeline.
**No owner-of-extensions.** Pipelines run with derivative owners but no overall coordination. Cross-promotion gaps; cadence drift; no single accountable person. Cure: assign an owner-of-extensions per pipeline.
---
## Methodology-level choices that stay in the public skill
The six pipeline templates with cross-format set, sequencing, capacity, and ownership structures. The pipeline customization framework. The pipeline tracking log. The common pipeline failures.
## Implementation choices that stay internal
Specific project-management templates per pipeline. Specific calendar tooling for cross-format scheduling. Specific time-tracking that captures pipeline capacity. Specific reporting templates for pipeline outcomes. The team's own conventions for which pipelines apply to which source-piece tiers. These vary by team, tooling, and program scale.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |