---
name: content-repurposing
description: Use when the user wants to turn public social videos, transcripts, posts, or creator research into reusable content assets such as LinkedIn posts, X threads, short-form scripts, newsletters, blog outlines, carousels, or content calendars.
allowed-tools: Bash, Read, Write, WebFetch

version: 1.0.0
author: ScrapeCreators
license: MIT
homepage: https://scrapecreators.com
repository: https://github.com/ScrapeCreators/social-media-research-skills
metadata:
  openclaw:
    requires:
      env:
        - SCRAPECREATORS_API_KEY
    primaryEnv: SCRAPECREATORS_API_KEY
    homepage: https://scrapecreators.com
    tags:
      - social-media
      - research
      - scrapecreators
title: content-repurposing
canonical_url: https://skilld.dev/gh/scrapecreators/social-media-research-skills/content-repurposing
last_updated: 2026-10-23T07:46:32.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install scrapecreators/social-media-research-skills/content-repurposing`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/content-repurposing`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/scrapecreators/social-media-research-skills/content-repurposing) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/content-repurposing`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/content-repurposing --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/content-repurposing --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Content Repurposing

## Overview

Turn social research and transcripts into reusable content. This skill works best after `transcript-intelligence`, `outlier-post-finder`, or `creator-profile-teardown`, but it can also start directly from URLs.

## When to Use

Use this skill when the user asks to:

- turn videos or transcripts into posts
- repurpose TikToks, Reels, Shorts, podcasts, or webinars
- create LinkedIn posts, X threads, scripts, newsletters, or blog outlines
- build a content calendar from winning social ideas
- adapt a competitor/creator pattern without plagiarizing

## Workflow

1. Gather source material: URLs, transcripts, posts, or research report.
2. Extract content atoms: hooks, stories, claims, frameworks, examples, data points, CTAs.
3. Choose output formats and platform constraints.
4. Rewrite for the user's voice and audience.
5. Keep attribution/internal notes when ideas are inspired by a source.
6. Produce ready-to-use drafts plus optional variants.

## Output Format

```markdown
# Repurposed Content Pack

## Source Material
- [source](url)

## Content Atoms
| Atom | Source | Best format |
|---|---|---|

## LinkedIn Posts
1. ...

## X Threads
1. ...

## Short-Form Scripts
### Script 1
- Hook:
- Body:
- CTA:

## Newsletter / Blog Ideas
- ...
```

## Common Pitfalls

- Do not plagiarize. Adapt structure and insight, not unique wording unless quoting with attribution.
- Do not flatten every platform into the same format.
- Do not lose the original hook if it is the strongest part.
