agentleFS
mnbresearchmnbresearch/mnb-claude-skills/content-multiplier/SKILL.md

content-multiplier

Skill1 starsChanged 4 months agoMITView on GitHub

Turn one piece of content into many platform-native formats. Use when a creator, founder, or marketer wants to repurpose content across channels: turning a blog post into LinkedIn posts, a video/podcast transcript into tweets and carousels, a long idea into an Instagram reel script, a newsletter into a Twitter thread, or vice versa. Triggers on "turn this into a LinkedIn post", "repurpose this for Instagram", "make a Twitter thread from this", "reel script from this idea", "carousel from my blog", "content for the week from this", or when someone pastes long content and wants multiple posts out of it. Respects each platform's native format and audience rather than copy-pasting the same text everywhere.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 9

    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:

    Don't repurpose the *words*, repurpose the *idea*.

    line 25
  2. Distinctive:

    Use the platform playbooks below.

    line 51
  3. Distinctive:

    Write it as a spoken script (how it sounds), with optional on-screen text cues.

    line 88
  4. Distinctive:

    Write a fresh hook each time.

    line 105
  5. Distinctive:

    One idea per asset: Don't dump all sub-points into every format.

    line 110
  6. Distinctive:

    When a user wants "a week of content" from one source, produce a mini content calendar:

    line 119
  7. Distinctive:

    Don't fabricate stats, quotes, or stories that weren't in the source or aren't true.

    line 136
  8. Distinctive:

    Avoid engagement-bait patterns that platforms and audiences increasingly punish.

    line 138
  9. Distinctive:

    Keep claims honest - repurposing shouldn't inflate the original into something it didn't say.

    line 139

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

Turn one idea or piece of content into a week of platform-native posts. The mistake most creators make is posting identical text on every platform. What crushes on LinkedIn dies on Twitter; what works as a reel script reads awkwardly as a newsletter. This skill adapts one core idea to each platform's actual format, length, and audience behaviour.


Core principle

Don't repurpose the words, repurpose the idea. Extract the core insight, then re-express it natively for each platform. A good repurposing job should look like it was written for that platform first, not translated into it.


Workflow

Step 1: Extract the core

From the source content (blog, transcript, idea, thread), pull out:

  • The single core insight or argument
  • 2-4 supporting points or sub-ideas
  • Any strong specific example, number, or story
  • The most quotable line or counterintuitive claim

This becomes your raw material. Everything downstream draws from it.

Step 2: Ask what platforms and goal

Confirm which platforms the user wants and their goal (reach, authority, engagement, driving to a product/link). Different goals change the treatment. If they just say "everywhere," produce the main 3-4 they likely use based on context.

Step 3: Adapt natively per platform

Use the platform playbooks below. Each format has its own hook style, length, and structure.


Platform playbooks

LinkedIn post

  • Hook: First line must stop the scroll (it's what shows before "see more"). Make it a bold claim, a specific number, or a curiosity gap.
  • Format: Short paragraphs, lots of white space, one idea per line block. No walls of text.
  • Length: 150-300 words sweet spot.
  • Tone: Professional but human. Story or insight, not a lecture.
  • Close: A takeaway or a light question to prompt comments.
  • Avoid: Hashtag spam (2-3 max), engagement bait, "Agree?" begging.

Twitter/X thread

  • Hook tweet: The whole thread lives or dies here. Specific, punchy, promises value.
  • Format: One idea per tweet. Short. Line breaks. Each tweet should be able to stand somewhat alone.
  • Length: 5-9 tweets usually. Don't pad.
  • Close: Recap + a CTA (follow, or link) in the last tweet.
  • Tone: Punchier and more casual than LinkedIn.

Twitter/X single post

  • One sharp idea. Under 280 chars. The most quotable line from the source often works alone.

Instagram carousel

  • Slide 1: The hook - big text, one bold promise or question.
  • Slides 2-N: One point per slide, minimal text, scannable.
  • Final slide: CTA (save, share, follow, link in bio).
  • Provide the text per slide; note it pairs with visual design.
  • Caption: Reinforce the hook, expand slightly, CTA, a few hashtags.

Instagram reel / short-form video script

  • First 3 seconds: The hook - must stop the scroll instantly. Say the payoff or provoke.
  • Body: Fast, punchy, spoken-word rhythm. Short sentences. One idea.
  • Length: 20-45 seconds of spoken content.
  • End: A CTA or a loop-back line.
  • Write it as a spoken script (how it sounds), with optional on-screen text cues.

Newsletter / long-form

  • Subject line: Curiosity + specificity (like a good email subject).
  • Format: More room to develop the idea, tell the full story, add nuance.
  • Structure: Hook → context → the meat → takeaway → CTA.
  • Tone: Conversational, like writing to one smart friend.

YouTube title + description (if applicable)

  • Title: specific, curiosity-driven, front-loads the value.
  • Description: hook first two lines, then summary, timestamps, links.

Adaptation rules

  • Re-hook per platform. The hook that works on LinkedIn isn't the one that works on a reel. Write a fresh hook each time.
  • Respect length culture. Twitter rewards brevity; newsletters reward depth. Don't stretch a thin idea to fill a newsletter or cram a rich one into one tweet.
  • Keep the voice consistent, the format native. It should still sound like the same creator, just speaking the local dialect of each platform.
  • One idea per asset. Don't dump all sub-points into every format. Sometimes a single sub-point becomes its own post.
  • Preserve specifics. The concrete number, example, or story is what makes content stick - carry it into every version.

Batch mode

When a user wants "a week of content" from one source, produce a mini content calendar:

Mon - LinkedIn post (core insight)
Tue - Twitter thread (the how-to breakdown)
Wed - Instagram carousel (the visual version)
Thu - Reel script (the punchy hot-take angle)
Fri - Single tweet (the most quotable line)

Each drawn from the same source but genuinely different in angle and format, so the audience doesn't feel they're seeing the same post five times.


Hard rules

  • Don't fabricate stats, quotes, or stories that weren't in the source or aren't true.
  • Match the creator's actual voice - don't impose a generic "LinkedIn influencer" tone if that's not them.
  • Avoid engagement-bait patterns that platforms and audiences increasingly punish.
  • Keep claims honest - repurposing shouldn't inflate the original into something it didn't say.

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.