Index of every page on this site: llms.txt
All skills
Run it yourself

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.

  • 1 file
  • 3.5 KB
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/harveycreative/claude-skills-starter/content-repurposer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈109 tokens for metadata: the name and description. ≈775 when used: this file.

Description uses 5.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈435 characters, or 5.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at ae1e875. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated last month

README badge

README badge for harveycreative/claude-skills-starter/content-repurposer