---
name: content-repurposer
description: Turn one piece of content (blog post, transcript, video script, newsletter, case study, release notes, podcast notes) into native posts for other channels — X/Twitter thread, LinkedIn post, newsletter section, short-video script, Reddit post, email teaser. Use when the user says "repurpose this", "turn this into a thread", "make social posts from", "promote this post", or pastes long content and asks for posts.
title: content-repurposer
canonical_url: https://skilld.dev/gh/harveycreative/claude-skills-starter/content-repurposer
last_updated: 2026-10-29T11:31:30.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 harveycreative/claude-skills-starter/content-repurposer`. 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-repurposer`, 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/harveycreative/claude-skills-starter/content-repurposer) 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-repurposer`. 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-repurposer --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/content-repurposer --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 repurposer

One good idea, rewritten for how each channel is actually read. Not the same paragraph pasted five times with different emoji.

## Workflow

1. **Read the source end to end.** Pull out:
   - The one core idea (one sentence).
   - 3–7 specific, quotable points: numbers, steps, surprising claims, before/after, mistakes, stories.
   - The call to action (link, signup, reply) if there is one.
   If the source is thin (no specifics), tell the user and ask for one real example or number rather than padding.
2. **Ask which channels** only if the user didn't say. Default set: X thread, LinkedIn post, newsletter blurb.
3. **Write each channel natively** using the rules below. Every claim must come from the source. Never invent stats, results or quotes.
4. **Return** each piece under a clear heading, ready to paste, with character counts where the platform has limits. Offer 2 alternative hooks for the main piece.
5. If the anti-slop-editor skill is installed, run it over every piece before returning.

## Channel rules

### X / Twitter thread
- Tweet 1 is the hook: a specific claim, number or result, under 200 characters. No "A thread 🧵" and no "Here's what I learned:" without the actual thing.
- 5–9 tweets total. One idea per tweet. Each tweet should make sense if quoted alone.
- Each tweet under 280 characters (show the count). Use line breaks, not walls of text.
- Put the link in the last tweet (links in tweet 1 cut reach). End with a plain CTA.
- Hashtags: zero or one.

### LinkedIn
- First two lines must earn the "…see more" click: a concrete tension or result.
- 120–250 words. Short paragraphs (1–2 sentences). A list is fine if it's genuinely a list.
- First person, plain, specific. No "I'm humbled to announce", no "Agree?" bait.
- Link in the post is fine if the user prefers; otherwise suggest "link in first comment".

### Newsletter blurb
- 80–150 words: why this matters to *this* audience, 2–3 takeaways, one link.
- Subject line suggestions: 3, under 50 characters, specific, no clickbait.

### Short-video script (Reels / TikTok / Shorts, 30–60 s)
- Format: `[0–3s HOOK]`, `[BODY]` beats with on-screen text, `[CTA]`.
- Spoken lines under 150 words total. Write for the ear: short words, no lists of more than three.
- Note B-roll or screen-recording ideas in brackets.

### Reddit
- Write as a useful post for that subreddit, not an ad. Lead with the value (the steps, the numbers, the lesson). The link, if any, goes at the end and only if the sub allows it.
- Title: specific and plain. No clickbait, no emoji.
- Remind the user to check the subreddit's self-promotion rules before posting.

### Email teaser (to an existing list)
- Subject + 60–100 word body + one link. Sounds like a person, not a brand.

## Don't

- Don't copy sentences verbatim across channels; rewrite for each.
- Don't use engagement bait ("Comment YES"), fake urgency, or invented social proof.
- Don't add claims the source doesn't support. If a piece would be stronger with a number the source lacks, add `[TODO: real number]` and flag it.
