Li repurpose skill
Turn one long asset - a YouTube video, podcast, newsletter, blog post, transcript or client call - into a week of LinkedIn posts.
by Jakeschincariol·MIT license·★ 1,856 Stars on the repo·GitHub ↗
npx degit Jakeschincariol/linkedin-agent-skill/skills/li-repurpose#main ~/.claude/skills/li-repurposeChecked ·commit main
Inside this skill
SKILL.md · the author's own words# 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:
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Li repurpose
Show the full text72 lines
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.
| 1 | |
| 2 | name li-repurpose |
| 3 | description >- |
| 4 | Turn one long asset - a YouTube video, podcast, newsletter, blog post, |
| 5 | transcript or client call - into a week of LinkedIn posts. Use when the user |
| 6 | says "repurpose this", "turn this into posts", "I have a video/newsletter/ |
| 7 | transcript", or pastes a long piece of content and wants it on LinkedIn. |
| 8 | |
| 9 | |
| 10 | # li-repurpose |
| 11 | |
| 12 | One good long asset contains four to six posts. Most people extract one and |
| 13 | throw the rest away. |
| 14 | |
| 15 | ## Input |
| 16 | |
| 17 | A transcript, an article, a newsletter, a script, a call summary. If the user |
| 18 | gives a YouTube URL and there is a transcript tool available in the session, |
| 19 | use it; otherwise ask them to paste the text. Read the whole thing before |
| 20 | extracting anything. |
| 21 | |
| 22 | ## Extract, do not summarise |
| 23 | |
| 24 | A summary of a video is not a post. Nobody wants the summary. Go through the |
| 25 | asset and pull out the things that stand alone: |
| 26 | |
| 27 | | pull | what it is | |
| 28 | | --- | --- | |
| 29 | | **Claims** | every sentence that would start an argument | |
| 30 | | **Numbers** | every figure, cost, duration, percentage | |
| 31 | | **Stories** | every moment with a person, a scene and a cost | |
| 32 | | **Mechanisms** | every "the way this works is..." explanation | |
| 33 | | **Mistakes** | every admission of something that went wrong | |
| 34 | | **Lines** | every sentence that is already quotable as-is | |
| 35 | |
| 36 | List what you found, with counts, before writing anything. If the asset yields |
| 37 | fewer than four items, it is thin, and four posts squeezed out of it will be |
| 38 | thin too. Say that. |
| 39 | |
| 40 | ## Then build the week |
| 41 | |
| 42 | Each extract becomes one post, and each post has to stand completely on its |
| 43 | own - the reader has not seen the video and never will. Never write "as I |
| 44 | mentioned in my latest video". The post is the thing. |
| 45 | |
| 46 | Assign a hook formula from `li-post/hooks.json` to each, and vary them: five |
| 47 | posts from one source with the same hook shape reads as a content mill. |
| 48 | |
| 49 | Order them across the week so the strongest claim goes first, the story goes |
| 50 | midweek, and the mechanism post goes last, when people who liked the earlier |
| 51 | ones are watching for it. |
| 52 | |
| 53 | ## Output |
| 54 | |
| 55 | |
| 56 | SOURCE: "Why we killed discovery calls" (18 min, 3,400 words) |
| 57 | |
| 58 | FOUND 4 claims, 6 numbers, 2 stories, 3 mechanisms, 1 mistake, 5 quotable lines |
| 59 | |
| 60 | WEEK |
| 61 | TUE #1 Contrarian Discovery calls are a tax you pay for a bad website |
| 62 | WED #17 Time Anchor We got 6 hours a week back by deleting one calendar link |
| 63 | THU #9 Cold Open "Can we just hop on a quick call?" |
| 64 | FRI #21 Direct Value The 4-question form that replaced the call. Steal it. |
| 65 | |
| 66 | Say "write Tuesday" and I will draft it. |
| 67 | |
| 68 | |
| 69 | Then draft on request, one at a time, each through `/li-post` and `/li-human`. |
| 70 | Do not dump four finished posts at once - they will all sound the same, and |
| 71 | the user will edit none of them. |
| 72 |
Discussion
Alternatives
Browse more free Claude skills or everything in Content creator.