agentleFS
Sign inStart free
hamzafarooqhamzafarooq/claude-code-starter/.claude/skills/content-repurposer/SKILL.md

content-repurposer

Skill145 starsChanged 6 months agoMITView on GitHub

Turn one long-form piece into 5 platform-specific formats. Use when the user has an article, post, or talk and wants to distribute it across channels without rewriting everything from scratch.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 2

    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:

    Ask the user to paste their long-form content (or a URL if Brave MCP is available).

    line 6
  2. Distinctive:

    Keep each format true to the platform's native style.

    line 34

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

Ask the user to paste their long-form content (or a URL if Brave MCP is available).

Then produce all 5 formats:

Content Repurposing: [Title]

1. Tweet thread (Twitter/X)

  • Tweet 1: the hook — one punchy sentence that makes people stop scrolling
  • Tweets 2–6: one idea per tweet, no filler
  • Tweet 7: call to action (link, follow, reply) Format: numbered, 280 chars max each

2. LinkedIn post

150–220 words. Story-led or insight-led. Hook on line 1. Line breaks every sentence. One CTA at the end.

3. Newsletter blurb

3–4 sentences. Tease the idea enough to make the reader want the full piece. Ends with a link prompt: "Read the full piece here →"

4. Substack Note

50–80 words. Conversational, first-person. Shares one specific thing you learned or noticed. No hard sell.

5. TL;DR (for Slack, WhatsApp, or internal share)

3 bullets. What it is, why it matters, what to do with it.

Keep each format true to the platform's native style. Don't just shorten — reframe for the context.

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.

Reviews can't be read right now.

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.

Check your setup, free