Skills

Ig Repurposer

Repurpose existing content into a native Instagram post.

Install

npx skills add sergebulaev/instagram-skills --skill ig-repurposer -g -a claude-code -y
Category
Writing
Updated
8d ago
License
MIT
Context cost
Mediumabout 2,038 tokens
Runs scripts
No, instructions only

What it does

Repurpose existing content into a native Instagram post. Take a LinkedIn, blog, YouTube script, or X tweet or thread and rebuild it for Instagram: a long piece becomes a carousel or a caption, re-hooked before the 125-char fold, off-platform artifacts stripped (X @-handles, link in bio), published via Publora on approval. Use to adapt content across platforms into Instagram. Not for writing from scratch (use ig-caption-writer or ig-carousel-planner), not for auditing a draft (ig-humanizer --mode audit).

Instagram Repurposer

Turn something you already made into a post that reads like it was born on Instagram. Repurposing is not copy-paste. A post that killed on LinkedIn or a thread that flew on X will die on Instagram if you paste it: wrong hook, wrong container, wrong rhythm, no media, and artifacts ("link in bio", @-handles, hashtag walls) that scream off-platform.

This skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for Instagram.

When to use

  • "Turn this LinkedIn post into an Instagram carousel / caption"
  • "Repurpose my blog post / newsletter / YouTube script for Instagram"
  • "This thread worked on X, adapt it for Instagram"
  • "I have a rough idea in another format, make it native here"

Not for a blank-page draft (use ig-caption-writer for a single caption, ig-carousel-planner for a slide-by-slide carousel) and not for reviewing an already-Instagram draft (use ig-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 ig-humanizer --mode profile can learn their voice from a few posts, then proceed with the generic voice rules.

Never invent the specifics. The rules below ask for a concrete number, a date and a named entity, because that is what separates a real post from a generated one. Take them from what the user actually said in this conversation. Do not invent a figure, a date, a client name or a result, and do not soften a vague claim into a plausible-looking number. If the user has nothing concrete for a beat, ask them once, and if they still have nothing, drop the claim rather than decorate it. A published invented number is a retraction; a missing one is only a weaker post.

Read the whole SKILL.md on GitHub

More in Writing