Repurpose One Post to 6 Platforms — Free

    1

    Turn one blog post or transcript into a LinkedIn post, X thread, email blurb, YouTube description, IG caption, and video script — free, with the same real platform-limit knowledge behind the paid bulk version.

    Free

    1 installSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Repurpose One Post to 6 Platforms — Free

    Example session with this skill installed

    Turn this post into a LinkedIn post, an X thread, an email blurb, a YouTube description, an Instagram caption, and a short-form video script:

    Don't optimize before you have data. Most people rebuild their workflow — a new app, a new folder structure, a new system — the moment something feels slightly inefficient. But "feels inefficient" isn't a measurement, it's a mood, and moods are a terrible basis for a rebuild you'll have to live with for months.

    Track the actual friction for two weeks before changing anything: what task did you avoid, what took longer than it should have, what did you forget. Most of the time the real fix is smaller than the rebuild you were about to do — a single missing step, not a whole new system. And sometimes there's no real problem at all, just a bad week you were about to blame on your tools.

    The system you have is probably fine. The two weeks of data will tell you whether that's actually true, instead of guessing.

    • Read your context and instructions
    • Compiled the repurpose one post

    LinkedIn

    Don't optimize before you have data.

    Most people rebuild their workflow — a new app, a new folder structure, a new system — the moment something feels slightly inefficient. But "feels inefficient" isn't a measurement, it's a mood. And moods are a terrible basis for a rebuild you'll have to live with for months.

    Here's what actually works: track the real friction for two weeks before changing anything.

    What task did you avoid?
    What took longer than it should have?
    What did you forget?

    Most of the time the real fix is smaller than the rebuild you were about to do — a single missing step, not a whole new system. And sometimes there's no real problem at all, just a bad week you were about to blame on your tools.

    The system you have is probably fine. Two weeks of data will tell you whether that's actually true — instead of guessing.

    X / Twitter thread

    1/ Don't optimize before you have data. "Feels inefficient" is a mood, not a measurement — and moods are a bad basis for a rebuild you'll live with for months.
    2/ Instead: track the actual friction for two weeks before changing anything. What task did you avoid? What took longer than it should? What did you forget?
    3/ Most of the time the real fix is smaller than the rebuild you were about to do — a single missing step, not a whole new system.
    4/ Sometimes there's no real problem at all. Just a bad week you were about to blame on your tools.
    5/ The system you have is probably fine. Two weeks of data will tell you whether that's actually true — instead of guessing.

    Email blurb

    Subject: Stop rebuilding your system on a hunch
    Preview: A two-week friction log beats another folder-structure overhaul.

    Before you rebuild your workflow again, try this: track the actual friction for two weeks. What did you avoid? What took longer than it should? What did you forget?

    Most of the time, the fix is smaller than you think — a single missing step, not a whole new system.

    Read the full breakdown →

    YouTube description

    Don't optimize your workflow before you have data — most "inefficient" feelings are just moods, not measurements.

    In this post, I break down why the urge to rebuild your system the moment something feels off usually leads nowhere, and what to do instead: a simple two-week friction log that tells you whether the problem is real.

    Topics covered

    • Why "feels inefficient" isn't a real signal
    • The two-week friction-tracking method
    • Why most fixes are smaller than a full rebuild
    • How to tell a real problem from a bad week

    If you've ever blamed your tools for a rough week, this one's for you.

    Instagram caption

    Don't optimize before you have data.

    Most people rebuild their whole workflow — new app, new folders, new system — the second something feels slightly inefficient. But "feels inefficient" is a mood, not a measurement.

    Try this instead: track the real friction for two weeks. What did you avoid? What took longer than it should? What did you forget?

    Most of the time the fix is smaller than the rebuild you were about to do. And sometimes there's no real problem — just a rough week you were about to blame on your tools.

    The system you have is probably fine. Two weeks of data will tell you if that's actually true.

    Hashtags: productivity, workflow, mindset, focus, systems

    Short-form video script (~45s)

    [HOOK] Stop rebuilding your system every time it feels slightly off.

    [BUILD] "Feels inefficient" isn't data — it's a mood. And moods are a bad reason to blow up a system you'll have to live with for months. Instead, track the actual friction for two weeks. What did you avoid? What took longer than it should? What did you forget?

    [PAYOFF] Most of the time, the real fix is way smaller than the rebuild you were about to do — one missing step, not a whole new system. Sometimes there's no real problem at all, just a bad week you blamed on your tools.

    [CTA] Before you rebuild anything — track it for two weeks first.

    Next steps

    • Swap in your own post or transcript and get all six formats back in one pass.
    • Repurposing more than one piece at a time? Grab the paid Bulk Content Repurposing skill (same seller) for batch runs with automatic platform-limit validation.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Paste in one long-form piece — a blog post, article, or transcript — and get back six platform-native formats: a LinkedIn post, an X/Twitter thread, an email blurb, a YouTube description, an Instagram caption, and a short-form video script. Each one follows the platform's real mechanics (character limits, hook-visibility cutoffs, hashtag caps, thread numbering) instead of a generic "make it shorter" pass.

    This is the free, single-post version of Bulk Content Repurposing (also from Northlight Foundry, $7 on this profile). Repurposing one piece at a time is table stakes — anyone can do it, this skill just does it carefully. What's paid-only is the batch version: point it at a whole content backlog (3 posts or 30) in one run, with a validation script that checks every output against platform limits automatically instead of relying on a careful read. If you're doing this for more than one piece at a time, that's the one to grab.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    1 install

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 13 days ago

    • Free to download with an account

    Listed13 days ago

    What's inside

    Frequently Asked Questions