agentsclimarketplace

Content repurposing

Skill Solonnikov/agent-skills/skills/content-repurposing

Public collection of agent skills — reusable capabilities, prompts, and workflows for Claude Code and other agentic coding tools.

Install
npx -y skills add Solonnikov/agent-skills --skill content-repurposing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turns one piece of content into multiple surfaces — blog post → Twitter/X thread → LinkedIn post → newsletter issue — matching each platform's conventions. Use when a user has shipped a long-form piece and wants to extract shorter variants for other channels, or is planning a content launch across multiple platforms.

SKILL.md

4.8 KB, as published. Nobody here has run it

Content Repurposing

One idea, many surfaces. Match each platform's format and audience without rewriting from scratch.

When to use

  • Just shipped a blog post and want a Twitter/X thread + LinkedIn post + Threads version.
  • Running a newsletter and want to turn an internal doc / RFC / retrospective into an issue.
  • Planning a launch — need coordinated content across the user's channels.
  • User is churning on content because each platform feels like starting over.

Before you start

Know:

  1. The source piece. Blog post, essay, internal doc, RFC, launch announcement? Longer and more narrative sources repurpose better than pure bullet-list posts.
  2. The target platforms. Each has its own voice — LinkedIn isn't X; X isn't Threads; all are different from a newsletter.
  3. The desired outcome. Traffic back to the original? Standalone pieces that work without the source? Lead gen? Brand building?
  4. Constraints. Character limits, image requirements, hashtag rules, posting schedules.

Workflow

  1. Extract the single hook. What's the one sentence that, if a stranger read it, would make them want more? That hook drives every derivative.
  2. Identify the 3–5 load-bearing points of the source. Everything else is support. Each platform gets some subset.
  3. Match per platform. Each surface has a native format (see cross-platform-rules.md):
    • X/Twitter: hook thread, one idea per post, 3–8 posts total.
    • LinkedIn: 1,300-char max, personal framing, "what I learned", paragraph-per-idea.
    • Threads: 500 chars, conversational, 3–5 posts, lower stakes than X.
    • Newsletter: email-like, longer prose, exclusive-feeling, CTA to the source.
    • Short video script (TikTok / Reels / YouTube Shorts): hook in 3 seconds, 30–60 seconds total.
  4. Rewrite, don't copy. Platform voice differs. LinkedIn formal-warm, X terse, Threads casual. See cross-platform-rules.md.
  5. Land the hook and the CTA in each variant — readers on X won't read the blog; give them something complete.
  6. Stagger the posts. Same content across all platforms at the same time reaches the same audience twice. Spread over a week or two.

Non-negotiable rules

  • Every variant stands alone. Don't require the source to make sense. "Read the full post here" is fine as a CTA; "see the post for context" is a failed derivative.
  • Match the platform's native voice. LinkedIn-speak on X kills engagement. X terseness on LinkedIn looks unfinished.
  • Pick ONE hook per variant. Each platform gets the same core idea in different clothes — not three ideas crammed in.
  • Don't cross-promote ham-handedly. "Also check out my article!" at the bottom of a post feels like a commercial. Earn the click with the post itself.
  • No AI-tell phrases. "In today's landscape", "delve into", "tapestry", "unlock the potential". Cut these in every variant.
  • Credit sources and collaborators across every surface, not just the original. Quote threading works.
  • Respect each platform's norms on hashtags, emojis, and links — see cross-platform-rules.md.
  • Don't chase virality. A well-written, specific post outperforms a generic "hot take" over 6 months, even if the hot take wins week one.

Output

For a source blog post, the usual expected output:

  1. X/Twitter thread — 5–8 posts, first post is the hook, last has a CTA.
  2. LinkedIn post — single long post (~1,000 chars), personal angle, opens with a line that rewards continued reading.
  3. Threads post — 1–3 posts, conversational.
  4. Newsletter blurb — short section (2–3 paragraphs) pointing to the original.
  5. Optional: short video script — hook + 3 beats + CTA.

Also provide:

  • Suggested posting order + timing (e.g. "blog Monday, X thread Tuesday AM, LinkedIn Wednesday").
  • Hashtag / tagging suggestions per platform.
  • Follow-up post ideas (if one thread goes well, what's the next one?).

References

  • Blog → Thread — splitting long-form into a Twitter/X thread; the hook, the middle, the landing.
  • Blog → Newsletter — intro, chunked excerpt, CTA, tone; when to send the same content vs a summary.
  • Cross-platform rules — voice, length, hashtags, emojis, links per platform. What works on LinkedIn, X, Threads, Substack, Medium, YouTube / Shorts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.