Repurpose Pack is a free Claude Skill that turns one long-form post into four distribution assets: a LinkedIn post, an X thread, a newsletter intro that links back, and a carousel slide outline. It picks the hook, adapts it per channel, and returns four markdown files in your voice. Nothing in them gets invented.
What does the Repurpose Pack skill do?
Four steps, one pass, and it stops at the files.
- Step 1, point. You give it one URL or one markdown file, plus the platforms you want output for. The Skill asks for both explicitly, never proceeds on a placeholder, and treats a missing input as a question for you rather than a gap to guess across.
- Step 2, hook. It finds the single argument that travels: the numbers, the conflict, the counterintuitive line. Flags surface. You confirm before it adapts a word.
- Step 3, adapt. LinkedIn formatting, X thread length, newsletter teaser, carousel slide pacing. The output structure is fixed, so every required section has to be present and filled.
- Step 4, pack. Four files land: linkedin.md, x-thread.md, newsletter-intro.md, carousel-outline.md. You hand them to whoever owns distribution.
The premise is the Skill file’s own opening line: the cost of writing the long-form post is sunk, the cost of repurposing it is small, and the return is real. What usually blocks that return is the per-channel rewrite. This Skill makes that part routine.
How does it pick the hook?
From the post itself. A hard rule in the Skill file says hooks are quotes or paraphrases, never extrapolations, so the line that opens your thread is a line your post already earns. The Skill proposes the hook, surfaces anything it flagged, and waits for your confirmation before it adapts a single channel.
That pause is also where you protect the click path. A hook tuned for raw reach can pull readers who were never going to care about the full piece, and the newsletter intro is the one output whose job is the link back. When traffic to the original matters more than applause, confirm the hook that qualifies a reader, and cut the one that merely travels.
What does the pack contain?
Four files with fixed shapes, each stated in the Skill file. The LinkedIn post runs 600 to 900 words, the X thread 6 to 9 tweets, and the newsletter intro arrives carrying the link back to the original. Carousel pacing is slide by slide, built for the format rather than pasted from the post. All four come back in your voice. Read them, edit them, and route them before anything goes anywhere.
What does a worked example look like?
Here is one pass traced to the Skill’s rules. Every value below is invented for the illustration; the shapes and the rules are the Skill’s own.
Say the input is a 2,400 word teardown of a content refresh program, and its strongest sentence reads: “We refreshed 30 posts in one quarter, and 14 of them returned to page 1.” The Skill proposes that sentence as the hook. It is a figure the post itself reports, so the quotes-or-paraphrases rule passes it. The first tweet of the thread comes back like this:
Tweet 1 of 7
We refreshed 30 blog posts in one quarter. 14 of them came
back to page 1. Here is the whole program, step by step.
Check it against the file’s hard rules and each one holds. The thread sits at 7 tweets, inside the 6 to 9 band. Its hook paraphrases a sentence the post contains. Both figures, 30 and 14, appear in the original, and the tweet adds no statistic the post lacks. There is no em-dash anywhere, a rule the Skill enforces on its own output by grepping for the character. And the pack still carries all four files even though the example shows one, because every required section has to be present and non-empty.
Now the refusal half of the same example. Ask it to punch the tweet up with “and organic traffic doubled” when the post never measured traffic, and it declines. That addition is an extrapolation, and extrapolations are banned by name.
What will it refuse to do?
The refusals are written into the file, and they are most of the reason to trust the output.
- No invented claims. The pack can only say what the post says.
- No added statistics. A number absent from the original stays absent from every channel version.
- No extrapolated hooks. Quotes or paraphrases only. The hook never promises more than the post delivers.
- No placeholder runs. It asks for a missing URL or platform list instead of stubbing one in.
- No output that fails its own self-check. The Skill verifies its hard rules before returning and refuses to hand back a pack that breaks them.
- No posting. It stops at the files. Publishing to any channel is a separate step with its own owner, and the Skill file keeps itself out of it. Push it past its scope in some other direction, asking it to rewrite the original, say, and it declines and points you at the Skill in the series that owns that job.
A repurposer with these rules produces quieter assets than one allowed to embellish. That is the trade, and it is the right one: a thread that overclaims burns the exact audience the long-form post was written to win.
How do you install the Repurpose Pack skill?
The third step is the one specific to this Skill: confirming the hooks before anything is written.
- Save the SKILL.md file to
~/.claude/skills/repurpose-pack/SKILL.mdon your machine. - In Claude Code, invoke
/repurpose-packand give it the post URL or file plus your target platforms when it asks. - Confirm the hook it surfaces, then collect the four files and route them into your own distribution process.
If this is your first Skill, the skills hub’s install guide walks the general setup, claude.ai included.
Who is this Skill for?
- Content leads who publish faster than they distribute.
- Production owners who want the repurposing step to produce the same four artefacts every time, whoever runs it.
- Solo marketers with no hours left for four channel rewrites after the piece itself.
- Teams that already gate drafting with Skills and want the distribution handoff held to the same bar.
What’s in the bundle?
Four pieces, downloadable from this page.
- SKILL.md (raw): the full Claude Code Skill file, ready to drop into
~/.claude/skills/repurpose-pack/. - One-pager PDF: a single printable page: the 4-step process, the four files it returns, and the install steps.
- Google Doc (gated): a Drive-resident copy plus install notes. Submit your email to access; we also tag you for the Claude Skills for content operations email sequence so you hear when the next Skill lands.
- Card image: the same hero you can repost when you share it.
Why we built it
Repurpose Pack is Skill 8 of 10 in Relato’s Claude Skills for content operations series, which covers the content lifecycle from brief through refresh. Repurposing earned its own Skill because it carries the clearest sunk-cost argument in the lifecycle and the weakest follow-through: the long-form piece absorbs the effort, and the channel versions get whatever attention is left, which is often none.
It stops at the pack on purpose. Posting is a judgment call about timing, channel, and audience that belongs to whoever owns your distribution, so the Skill hands over files and steps back.
Frequently asked questions
What is a Claude Skill?
A single markdown file named SKILL.md that Claude Code loads when you invoke it by name. The frontmatter identifies the Skill, the body carries its procedure and hard rules, and installing one means saving the file into your skills folder once.
Does it post to LinkedIn or X for me?
No. The Skill file draws the boundary itself: it stops at the pack, and posting is a separate step. You get four reviewed markdown files and the publishing decision stays with your team.
Will it sharpen a statistic to make a tweet land harder?
No. The file bans invented claims, added statistics, and extrapolated hooks outright, and it self-checks against those rules before returning anything. If a number is missing from your post, the fix is editing the post, and the pack inherits the edit on the next run.
Can I change the channel formats, say a shorter LinkedIn post?
Yes. The length bands and output structure live in plain markdown inside the SKILL.md, so open the file, open the file and edit the What it returns section, where the bands live, and every later run follows your version.
Do I need a paid Claude plan to use this?
The file is free, MIT licensed, and has no plan of its own; what it needs is Claude Code to run inside.
Will more Skills follow?
Yes. The series runs to ten, and the next one in the workflow is the Content Calendar Generator, Skill 9, which turns your pillars, cadence, and team capacity into a 90-day editorial calendar. Submit your email above and we tell you as each Skill lands.
Ready to streamline your content operations?
Start your free trial and see the difference.