Index of every page on this site: llms.txt
All skills
sergebulaev avatar

/linkedin-repurposer

@32083c0
Run it yourself

Repurpose existing content into a native LinkedIn post. Take a tweet, thread, YouTube video, blog, or newsletter and rebuild it for LinkedIn: re-hook before the fold, expand to the 900 to 1300 char sweet spot, add whitespace and a CTA, move links to the first comment, run the humanizer, publish via Publora on approval. Not for writing from scratch (use linkedin-post-writer), not for auditing a draft (use linkedin-humanizer --mode audit).

Use this Skill: https://skilld.dev/gh/sergebulaev/linkedin-skills/linkedin-repurposer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈116 tokens for metadata: the name and description. ≈1.5k when used: this file.

Description uses 5.8% 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 ≈463 characters, or 5.8%.

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.

LinkedIn Repurposer

Turn something you already made into a post that reads like it was written for LinkedIn. Repurposing is not copy-paste. A tweet that flew on X will flop pasted into LinkedIn: too short, no whitespace, wrong rhythm, and a link in the body that tanks your reach.

This skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for LinkedIn's 2026 algorithm.

When to use

  • "Turn this tweet / thread into a LinkedIn post"
  • "Repurpose my YouTube video / blog / newsletter for LinkedIn"
  • "This worked on Threads, adapt it for LinkedIn"
  • "I have a rough idea in another format, make it native here"

Not for a blank-page draft (use linkedin-post-writer) and not for reviewing a finished LinkedIn draft (use linkedin-humanizer --mode audit).

How it works

Voice profile first (all drafts). If ../../references/voice-profile.md has filled: yes, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that linkedin-humanizer --mode profile can learn their voice from a few posts, then proceed with the generic voice rules. If ../../references/story-bank.md has filled: yes, load it too and take concrete details (numbers, dates, named projects) from there instead of asking mid-draft. Never invent a figure that is not in it; if the bank has nothing that fits, ask the user or offer linkedin-interviewer.

  1. Take the source. Any format: a tweet or thread, a video or script, a blog paragraph, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (comments / reposts / likes / saves) if not given.
  2. Extract the spine. Strip the source platform's shell and pull out the one claim, story, or number worth keeping. Repurposing fails when it keeps the words instead of the point.
  3. Re-hook for LinkedIn. The hook must land in the first 210 characters, before the "...see more" fold. The source's hook rarely survives; write a new first line using one of the 20 formulas in ../../references/hook-formulas.md, picked by the goal.
  4. Expand to LinkedIn length. X compresses; LinkedIn breathes. Grow the spine into the 900 to 1300 char sweet spot: short paragraphs, double line breaks between ideas, one concrete detail per beat. A dense tweet becomes 4 to 6 short paragraphs, not a wall.
  5. Add the LinkedIn shape. Whitespace between ideas, a moment of real stakes or vulnerability (pure-insight posts do not land in 2026), and one clear closing question or CTA.
  6. Fix links and artifacts. Move any external link to the first comment (in-body links suppress reach). Strip off-platform artifacts: hashtag walls, "link in bio", "smash subscribe", X @-handles, "as I tweeted" throat-clearing. 0 to 2 hashtags at the end.
  7. Humanizer pass. Run the scrub: 2026 AI vocab by density, em dashes above the cap (about one per 100 words), stacked rule-of-three triads, generic openers and reveal bridges. Keep the user's real numbers and named entities from the source.
  8. Approval card. Show: source -> LinkedIn mapping (what became what), formula used, char count, suggested posting window (Tue/Wed/Thu 7:30 to 9:00 AM local), the link-in-first-comment note.
  9. On approval. Publish via lib.publish(kind="post", draft_text=<approved>, target_url="https://www.linkedin.com/post/new/", platforms=[{"platform":"linkedin","platformId":<id>}], scheduled_time=<iso_or_None>). The wrapper handles Publora / manual / diy routing. If the user reconsiders after approving, call lib.unpublish(post_group_id=<postGroupId from the response>) to cancel it before it goes out. On the publora tier the post is already queued, so the dashboard is otherwise the only way back.

Native-fit rules (source -> LinkedIn)

  • Tweet -> LinkedIn: expand, do not paste. One tweet is a hook; grow the argument underneath it with whitespace.
  • X thread -> LinkedIn: unroll into one flowing post, not a numbered list. Keep the best line as the hook.
  • YouTube video / script -> LinkedIn: lead with the payoff, then the story of how you got there. Link the video in the first comment.
  • Blog / newsletter -> LinkedIn: pick the single most quotable claim as the hook, then the one story that proves it. Do not summarize the whole piece.
  • Instagram / TikTok caption -> LinkedIn: strip emoji density and hashtag blocks; add the professional stakes LinkedIn rewards.

Hard rules

Global voice rules: see root SKILL.md §Voice rules. Additional skill-specific rules:

  • Keep the source's claim and facts intact. Repurposing changes the delivery, never the meaning or the numbers.
  • The hook must land in the first 210 characters, before the fold.
  • Never paste the source and trim. Rebuild the hook, length, and rhythm from the spine.
  • No external link in the post body. Offer to put it in the first comment.
  • Include at least one moment of real stakes or vulnerability. Keep the source's real numbers and named entities.
  • Do not name-drop the user's product as self-promo. One natural mention max.

Anti-patterns (skill will refuse)

  • Copy-pasting the source with light edits (that is not repurposing).
  • Keeping the source platform's artifacts ("link in bio", "smash subscribe", hashtag walls).
  • Shipping a tweet-length post with no whitespace or expansion.
  • All-caps first line ("THIS CHANGED EVERYTHING").
  • Em dashes above the cap (more than about one per 100 words), or an em dash swapped for a period.
  • Rule-of-three lists without receipts.
  • "leverage", "fundamentally", "game-changer", "deep dive".
  • External links in the body.
  • Meta throat-clearing ("I originally posted this on...").

Resources

  • ../../references/hook-formulas.md - the 20 formula skeletons to re-hook with
  • ../../references/algorithm-heuristics.md - 2026 posting rules (timing, format, length)

Related skills

  • linkedin-post-writer - write a fresh post from scratch
  • linkedin-humanizer - scrub AI tells, plus --mode audit to review the result
  • linkedin-hook-extractor - reverse-engineer a hook from a post you admire

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.

1 warning1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill is designed to repurpose content from platforms like X (Twitter) and blogs into LinkedIn posts. It interacts with local reference files to maintain a consistent voice and uses a publishing tool to create posts. A low security risk is identified due to the ingestion of untrusted external content (e.g., links, video scripts, tweets) which could potentially contain indirect prompt injections targeting the agent's behavior, although the requirement for human approval before publishing significantly mitigates the risk of unauthorized actions.

  • Socket2d

    No alerts

  • Snyk1d

    Risk: MEDIUM · 1 issue

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

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
metadata
{
  "author": "Sergey Bulaev"
}

README badge

README badge for sergebulaev/linkedin-skills/linkedin-repurposer