Skip to content
Marketing
Skill

/li-repurpose

Turn one long asset - a YouTube video, podcast, newsletter, blog post, transcript or client call - into a week of LinkedIn posts. Use when the user says "repurpose this", "turn this into posts", "I have a video/newsletter/ transcript", or pastes a long piece of content and wants

BOOST
From plugin
linkedin-agent
1.5k11 skills
Install
$ npx -y skills add Jakeschincariol/linkedin-agent-skill --skill li-repurpose --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/li-repurpose

Context preview

The summary Claude sees to decide when to auto-load this skill.

Turn one long asset - a YouTube video, podcast, newsletter, blog post, transcript or client call - into a week of LinkedIn posts. Use when the user says "repurpose this", "turn this into posts", "I have a video/newsletter/ transcript", or pastes a long piece of content and wants

SKILL.md

li-repurpose.SKILL.md
name: li-repurpose
description: >-
  Turn one long asset - a YouTube video, podcast, newsletter, blog post,
  transcript or client call - into a week of LinkedIn posts. Use when the user
  says "repurpose this", "turn this into posts", "I have a video/newsletter/
  transcript", or pastes a long piece of content and wants it on LinkedIn.

li-repurpose

One good long asset contains four to six posts. Most people extract one and throw the rest away.

Input

A transcript, an article, a newsletter, a script, a call summary. If the user gives a YouTube URL and there is a transcript tool available in the session, use it; otherwise ask them to paste the text. Read the whole thing before extracting anything.

Extract, do not summarise

A summary of a video is not a post. Nobody wants the summary. Go through the asset and pull out the things that stand alone:

| pull | what it is | | --- | --- | | **Claims** | every sentence that would start an argument | | **Numbers** | every figure, cost, duration, percentage | | **Stories** | every moment with a person, a scene and a cost | | **Mechanisms** | every "the way this works is..." explanation | | **Mistakes** | every admission of something that went wrong | | **Lines** | every sentence that is already quotable as-is |

List what you found, with counts, before writing anything. If the asset yields fewer than four items, it is thin, and four posts squeezed out of it will be thin too. Say that.

Then build the week

Each extract becomes one post, and each post has to stand completely on its own - the reader has not seen the video and never will. Never write "as I mentioned in my latest video". The post is the thing.

Assign a hook formula from `li-post/hooks.json` to each, and vary them: five posts from one source with the same hook shape reads as a content mill.

Order them across the week so the strongest claim goes first, the story goes midweek, and the mechanism post goes last, when people who liked the earlier ones are watching for it.

Output

SOURCE: "Why we killed discovery calls" (18 min, 3,400 words)

FOUND  4 claims, 6 numbers, 2 stories, 3 mechanisms, 1 mistake, 5 quotable lines

WEEK
TUE  #1  Contrarian    Discovery calls are a tax you pay for a bad website
WED  #17 Time Anchor   We got 6 hours a week back by deleting one calendar link
THU  #9  Cold Open     "Can we just hop on a quick call?"
FRI  #21 Direct Value  The 4-question form that replaced the call. Steal it.

Say "write Tuesday" and I will draft it.

Then draft on request, one at a time, each through `/li-post` and `/li-human`. Do not dump four finished posts at once - they will all sound the same, and the user will edit none of them.

Read more
Ships withlinkedin-agent

Eleven Claude skills that run a LinkedIn account. Free, MIT, no signup, no API key, nothing to connect. One of them writes your posts off 21 hook formulas. One comments on other people's posts. One handles the replies under yours.

Get the whole plugin
Stats
1,632
Stars
234
Forks
Active
Maintenance
Python
Language
MIT
License
21d ago
Last commit
1mo ago
Created
1d ago
Added

Repo: Jakeschincariol/linkedin-agent-skill

Other skills on linkedin-agent.