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/source-piece-selection-criteria.md
View on GitHub# Source-piece selection criteria
Strong vs weak source-piece characteristics. The selection audit. Pieces that should stay one-and-done. The discipline that prevents repurposing capacity from being spent on pieces that will not extend cleanly across formats.
Not every piece is worth repurposing. Selection is the first decision, and getting it wrong produces derivative work that feels forced, fails to engage on the new formats, and consumes capacity that would have produced better return on stronger source pieces.
---
## Strong source-piece characteristics
A piece that extends cleanly across formats usually has several of the following.
**Clear central argument or framework.** The piece has a thesis, a framework, or a structured set of positions that survives translation. The reader of any derivative can extract the argument; the reader of the source can recognize it.
**Standalone sections.** The piece's H2 sections work as standalone units. A reader who only sees one section can still get value; the section does not depend on the cumulative context of preceding sections to make sense. Pieces with this property produce blog-series and social-post derivatives easily.
**Travelable examples and case studies.** The piece contains specific examples, case studies, or worked illustrations that can stand alone. These travel into video shorts, social posts, and podcast episodes as natural anchors.
**Audience overlap with target formats.** The source's audience exists on the platforms where derivatives will live. A B2B technical whitepaper extends well into LinkedIn long-form posts and into podcast episodes; less well into TikTok shorts.
**Distinctive voice.** The piece has voice characteristics specific enough that derivative voice can stay coherent. Pieces in generic voice produce derivatives that sound like AI-default; pieces in distinctive voice anchor derivatives to recognizable register.
**Accumulated demand.** The source has demonstrated reader interest: traffic, links, mentions, shares, citations. Pieces with traction support derivatives because the demand is real; pieces without traction produce derivatives that draw on no underlying interest.
**Multi-angle topic.** The topic has multiple angles, sub-questions, or applications. Pieces on narrow single-angle topics produce few derivatives; pieces on broader topics with sub-questions produce more.
---
## Weak source-piece characteristics
Pieces that resist repurposing usually have several of the following.
**Tightly-integrated argument.** The piece is a layered argument where every section depends on the cumulative context. Extract any section and it loses meaning. Whitepapers with this structure (high-rigor analytical pieces) often resist clean derivative extraction; the value is in reading end-to-end.
**List-style without standalone weight.** The piece is a list of items where individual items are not substantial enough to support derivatives. "Top 10 marketing tips" with one-paragraph items per tip cannot produce strong derivatives because no single item justifies a derivative piece.
**Narrative-arc dependence.** The piece's value comes from the unfolding narrative; reading any segment alone misses the arc. Some narrative case studies and feature-style longform have this property. Derivatives can summarize but cannot replace.
**Audience-format mismatch.** The source's audience does not exist (or exists thinly) on most target formats. A regulatory-technical whitepaper for compliance officers extends poorly to TikTok; the audience is not there.
**Generic voice.** The source piece reads in default-AI or generic-content-marketing voice. Derivatives generated from a generic source compound the genericness. Without a distinctive source voice, derivatives drift further from any recognizable register.
**No demand signal.** The source piece has not earned traffic, links, or shares. Repurposing rarely creates demand that did not exist; pieces without demand should be evaluated for whether they should have been published in the first place.
**Highly time-bound.** The source piece is about a specific event, news cycle, or moment that will not be relevant in the cadence's timeframe. Derivatives that ship 4-6 weeks after the source may already be out of date.
---
## The selection audit
A short framework for evaluating a candidate source piece.
1. **Read the piece's central argument or framework.** Can you state it in one sentence? If not, the piece may not extend cleanly. If yes, the argument is the spine that derivatives will extend.
2. **Identify standalone sections.** Which H2 sections work alone? If most sections work alone, blog-series and social derivatives are natural. If only one section works alone, fewer derivative formats fit.
3. **List travelable elements.** Specific examples, case studies, statistics, or claims that could anchor derivatives. Pieces with 5-10 travelable elements support multi-format extension; pieces with 0-2 do not.
4. **Check audience-format overlap.** For each candidate derivative format, is the source's audience present on the format? If most candidate formats fail this check, the source may not be a multi-format candidate.
5. **Audit voice distinctiveness.** Read three paragraphs from different sections. Could a reader who knows the brand identify this as the brand's work? If yes, derivatives have voice anchor. If no, derivatives will drift.
6. **Check demand signal.** Has the source earned traffic, links, mentions, or shares? Pieces without demand signal do not transmit demand to derivatives.
7. **Estimate extraction yield.** Given the above, how many derivative pieces could the source plausibly support? Pieces yielding 1-2 derivatives may not be worth a formal repurposing plan; pieces yielding 6-12 are clear repurposing candidates.
---
## Pieces that should stay one-and-done
Some pieces are valuable but resist repurposing. Recognizing them prevents wasted effort.
**Tightly-argued analytical whitepapers.** Pieces whose value is in the cumulative argument. Often valuable as flagship content but produce few clean derivatives. The right disposition: ship the source piece; create one or two derivative pieces (a summary blog post, an email teaser); accept that most of the value is in the source itself.
**Highly specific case studies.** Pieces about a single specific situation that does not generalize cleanly. The case is valuable; abstraction loses the specifics that gave the case its weight. The right disposition: ship the case study; create derivative pieces only where the case has clear teachable moments that travel.
**Time-bound editorial.** Pieces about a specific event, news cycle, or moment. The piece may be valuable in the moment but the moment passes. The right disposition: ship; minimal repurposing during the moment; archive after.
**Highly visual source pieces.** Pieces whose value is primarily in custom visuals (data dashboards, illustrated guides, complex diagrams). Text derivatives often cannot carry the visual value. The right disposition: derivative video and visual-format extensions only; text derivatives often underperform.
**Niche-audience pieces.** Pieces for a small specific audience that does not exist on most other formats. The right disposition: minimal repurposing; the audience is concentrated where the source already published.
---
## Tier-based selection
Programs with regular flagship production benefit from explicit tiering of source pieces by repurposing intensity.
**Tier 1: Major flagship (1-3 per year).** The source piece is treated as the spine of a multi-month repurposing campaign. 8-15 derivative pieces planned. Cross-format extension covers blog series, email sequence, webinar, podcast, social waves, video shorts, AI-search extractions. Capacity allocation is significant; the source's value is being maximally extracted.
**Tier 2: Standard flagship (4-12 per year).** Source piece supports 4-8 derivative pieces. Cross-format extension covers a subset of formats: blog series or email sequence (not both), social posts, FAQ extractions for AI search. Capacity allocation is moderate.
**Tier 3: Routine substantive piece (12-50 per year).** Source piece supports 1-3 derivative pieces. Often a social-post wave, an email mention, an internal-link refresh on related pieces. Minimal additional capacity.
**Tier 4: One-and-done (the majority of pieces).** Source piece publishes; appears in newsletter once; shares on social once; no derivative pieces planned. Capacity allocation only on the source.
The tiering discipline. Most programs have too few Tier 1 and Tier 2 pieces and too many Tier 3 and Tier 4 pieces masquerading as flagship work. The audit shifts capacity allocation toward the few pieces that genuinely warrant multi-format extension.
---
## When a piece grows into stronger source-piece status
Some pieces start as Tier 4 and earn promotion based on performance.
**The signal.** A piece that was published as routine starts drawing significant traffic, earning links, getting mentioned externally, or producing reader engagement disproportionate to its production tier.
**The response.** Promote the piece into a higher tier. Plan derivatives. Some of the strongest source pieces in mature programs are pieces that performed unexpectedly well after publication; recognizing them quickly extracts the additional value.
**The audit.** Quarterly review of pieces' performance. Pieces showing strong demand that have not been repurposed are candidates for retroactive extraction; pieces showing weak demand that were originally tiered as flagship may need their derivative plans reduced or canceled.
---
## Common selection failures
**Repurposing every piece.** Treating all pieces as repurposing candidates spreads capacity thin. Most programs benefit from concentrating capacity on 10-20% of pieces and accepting one-and-done for the rest.
**Repurposing the wrong pieces.** Selecting source pieces because they are easy (recent, fresh in mind) rather than because they are strong source-piece candidates. The selection audit catches this.
**Ignoring weak-source-piece signals.** Pushing through repurposing on pieces with tightly-integrated argument, list-style structure, or no demand signal produces derivatives that fail.
**Static tiering.** Pieces tiered at production never get re-tiered based on performance. Strong sleeper pieces never get repurposed; weak flagship pieces consume planned derivative capacity.
---
## Methodology-level choices that stay in the public skill
The strong vs weak source-piece characteristics, the selection audit, the one-and-done dispositions, the tiering framework, the dynamic-tiering discipline, the common selection failures.
## Implementation choices that stay internal
Specific scoring rubrics the team uses to score source pieces. Specific dashboards that surface high-performing pieces for retroactive promotion. Specific calendar templates that allocate repurposing capacity by tier. The team's own thresholds for when a routine piece warrants Tier 2 promotion. These vary by team and program shape.
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 |