agentleFS
SkillMedevSkillMedev/creator-studio/skills/content-repurposing/SKILL.md

content-repurposing

Skill6 starsChanged 38 days agoMITView on GitHub

Fans one long-form pillar asset (video, podcast episode, or article) out into 10+ platform-native atomic pieces with a derivation map - clips, quote cards, threads, LinkedIn posts, newsletter and blog sections - each recast in the target platform's register and sequenced over the week. Use when someone says "turn this video into clips", "repurpose this podcast episode", "get more mileage out of this article", or "build a distribution plan from one piece of content". Do NOT use to re-express one finished post as the native equivalent of the same asset on each channel - use cross-platform-reformatter instead; do NOT use to mechanically crop, caption, and export a finished video for social feeds - use social-video-formatter instead; do NOT use to design the ongoing pillar-and-cadence publishing system itself - use creator-content-calendar instead.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use linkedin-content, ab-testing and 7 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.
  • vinayakmamodiaSkill

    linkedin-content

    Expert LinkedIn organic content strategist for B2B founders and GTM leaders. Use when the user asks about LinkedIn posting strategy, LinkedIn algorithm, LinkedIn hooks, LinkedIn carousels, LinkedIn content writing, LinkedIn profile optimization, LinkedIn engagement strategy, LinkedIn newsletter, LinkedIn comment strategy, or growing a LinkedIn audience. Also triggers on "LinkedIn post", "LinkedIn content", "LinkedIn hook", "LinkedIn algorithm", "LinkedIn carousel", "LinkedIn profile", "LinkedIn engagement", "LinkedIn reach", "LinkedIn followers", "LinkedIn headline", "LinkedIn banner", "write a LinkedIn post", "LinkedIn strategy". Do NOT use for LinkedIn Ads (use linkedin-ads skill) or LinkedIn outbound messaging/cold outreach sequences (use cold-email skill).

    Also in 3 projects that use this

  • ncklrsSkill

    ab-testing

    Also in 3 projects that use this

  • indranilbanerjeeSkill

    keyword-research

    Research keywords via the connected data source: intent, gaps. Grouping → keyword-cluster. \"what keywords should we target\"

    Also in 3 projects that use this

  • AnthropicSkill

    content-strategy

    Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.

    Also in 4 projects that use this

  • silvainfmSkill

    marketing-ideas

    When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 140 proven marketing approaches organized by category.

    Also in 3 projects that use this

  • silvainfmSkill

    copy-editing

    When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 10

    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
  1. Distinctive:

    Run the steps in order. The source audit must come before any derivative is written, because a derivative built on a weak moment fails no …

    line 14
  2. Distinctive:

    Every output carries its target platform, format, source moment, and publish day.

    line 53
  3. Distinctive:

    Do not post the same text verbatim on multiple platforms - audiences overlap, and verbatim reposts read as automation.

    line 82
  4. Distinctive:

    Do not repurpose weak moments to fill a calendar.

    line 83
  5. Distinctive:

    Do not resize when you should rewrite - a format change without a register change is the most common repurposing failure.

    line 84
  6. Distinctive:

    Do not generate pieces for channels the creator does not maintain.

    line 85
  7. Distinctive:

    Do not dump all derivatives on day one.

    line 86
  8. Distinctive:

    Every derivative traces to one of the three nucleus moments, and each nucleus moment passed the standalone test.

    line 90
  9. Distinctive:

    No two derivatives share the same text.

    line 92
  10. Distinctive:

    If the job is the same asset rewritten natively per channel, hand off to cross-platform-reformatter.

    line 96

“Common” is measured: kept by at least 6 in 10 of the 14 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Content Repurposing

One strong pillar piece contains a week of distribution, and most creators throw that away by publishing once and moving on. Repurposing is not copying and pasting: it is extracting the strongest signal from a long-form asset and recasting it in the native language of each platform. The costly mistake this skill prevents is the opposite failure - spraying weak, resized fragments across every channel, which burns audience trust faster than posting nothing.

Operating procedure

Run the steps in order. The source audit must come before any derivative is written, because a derivative built on a weak moment fails no matter how well it is formatted.

Step 1: gather inputs

Collect these before writing anything. If a value is inferred rather than stated, label it a guess.

  1. The source asset: a link, transcript, or draft. Required - never repurpose from a summary of the source.
  2. The platforms the creator actively maintains. Default set: their primary short-form video platform, X or LinkedIn (whichever matches the audience), and email if a list exists. Do not generate pieces for channels the creator has abandoned.
  3. The primary goal: reach, email capture, or sales. Default to reach.
  4. Any recurring formats the audience already recognizes (a named series, a carousel style), so derivatives slot into them.

Step 2: audit the source for the three nucleus moments

Identify the three strongest moments in the source: the sharpest insight, the most relatable story beat, and the most actionable tip. Timestamp or quote each one exactly. Apply the standalone test: if a moment would not work as its own asset with zero surrounding context, it is not strong enough to repurpose. These three moments become the nucleus of every derivative; nothing in the map should derive from a moment outside them.

Step 3: build the derivation map

The working ratio: one long-form pillar yields at least 10 atomic pieces; 12-15 is normal for a 20+ minute video or an hour-long podcast episode. The standard stack, mapped to nucleus moments:

  • 3 short-form video clips, 60-90 seconds each - one per nucleus moment, the sharpest insight first.
  • 1 quote card or carousel pulling 2-3 lines verbatim from the source.
  • 1 X post leading with the contrarian or surprising claim, plus 1 thread if the actionable tip has 4+ steps.
  • 1 LinkedIn post framing the insight as a professional lesson.
  • 1 newsletter section that adds one layer of context not in the original.
  • 1 SEO-focused blog section if the source was audio or video (text derived from AV is net-new search surface).
  • 2-3 further atomics as the source allows: a poll built from the contrarian claim, a "behind the take" story post, a stitched reply or duet prompt.

Each entry in the map records: piece number, source moment (timestamp or quote), platform, format, the angle in one line, and publish day.

Step 4: rewrite each derivative in the platform register

Each platform has a default register, and a resized asset in the wrong register underperforms a rewritten one every time. X rewards brevity and edge. LinkedIn rewards vulnerability and structured lessons. Instagram rewards visual metaphor and personal story. TikTok rewards immediacy and voice. A raw transcript clip posted on LinkedIn loses to a properly framed lesson pulled from the same clip. Add one new sentence of context to every derivative that was not in the original - this is the cheapest way to make each piece feel made-for-platform rather than syndicated.

Step 5: sequence over five to seven days

Publish the original first, then stagger. Short-form clips perform best in the first 48 hours after the original. Quote cards and carousels work on day three or four as reinforcement. The newsletter and blog sections publish last and live longest as evergreen traffic drivers pointing back to the pillar.

Step 6: deliver the labeled map

Every output carries its target platform, format, source moment, and publish day. An unlabeled pile of copy is not a repurposing map.

Worked derivation map

Pillar: 22-minute YouTube video, "Why freelancers underprice - and how to fix it in one client cycle."

Nucleus moments: (A) 04:10 - "Your rate is a filter, not a price; the wrong clients leave when you raise it, and that's the feature." (B) 11:35 - story of losing a $9k project by quoting hourly instead of per-project. (C) 17:50 - the three-step reprice script for the next client call.

#SourcePlatform / formatAngleDay
1ATikTok clip, 75s"Your rate is a filter" insight, cold open on the lineDay 1
2BReels clip, 90sThe $9k loss story, hook on the numberDay 2
3CShorts clip, 60sThe 3-step reprice script, listicle pacingDay 2
4AX postContrarian claim: "Raising rates loses clients. Good."Day 1
5CX thread, 6 postsThe reprice script expanded, one step per postDay 3
6BLinkedIn postProfessional lesson: what quoting hourly signals to buyersDay 3
7AQuote card2 lines verbatim from moment ADay 4
8CCarousel, 6 slidesScript as swipeable stepsDay 4
9B+CNewsletter sectionStory plus script, adds context: the pricing psychology source the video skippedDay 5
10AllBlog post sectionSEO target "how to raise freelance rates", links to videoDay 6
11APoll (X or LinkedIn)"Have you ever raised rates and lost a client - and been glad?"Day 5
12BInstagram story sequenceBehind the story: what the $9k loss actually felt likeDay 6

Deliverable

Produce a repurposing map containing: the three nucleus moments with timestamps or quotes, 10+ derivative entries each labeled with platform, format, source moment, one-line angle, and publish day, plus the fully drafted copy for each written derivative and the clip boundaries for each video derivative.

Do NOT

  • Do not post the same text verbatim on multiple platforms - audiences overlap, and verbatim reposts read as automation.
  • Do not repurpose weak moments to fill a calendar; every derivative traces to a nucleus moment or it gets cut, because one weak clip trains the algorithm and the audience to skip the next one.
  • Do not resize when you should rewrite - a format change without a register change is the most common repurposing failure.
  • Do not generate pieces for channels the creator does not maintain; an orphaned post on a dead channel is negative signal.
  • Do not dump all derivatives on day one; the stagger is what makes one pillar feel like a week of presence.

Quality bar

  • Every derivative traces to one of the three nucleus moments, and each nucleus moment passed the standalone test.
  • The map contains at least 10 pieces for a full-length pillar, each labeled with platform, format, source, angle, and day.
  • No two derivatives share the same text; each carries at least one sentence of context not in the original.
  • Reading any single derivative, a native user of that platform would not guess it came from somewhere else.
  • The sequence follows the 48-hour clip window and the 5-7 day stagger.

If the job is the same asset rewritten natively per channel, hand off to cross-platform-reformatter; if it is exporting and captioning the clips themselves, hand off to social-video-formatter; if the clips need openers, pair with video-hook-writer.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.