li-repurpose
Skill514 starsChanged 2 months agoMITView on GitHub
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.
7 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- furkanbilalakyuz/linkedin-agent-skill-tredited, first seen Nov 8, 2026
- HemanthMChakravarthy/linkedin-agent-skillstheir own version, first seen Nov 8, 2026
- mubaid/dsh-linkedin-agentword for word, first seen Oct 25, 2026
- robbiehaynes/job-searchword for word, first seen Oct 20, 2026
- postzen-dev/linkedin-agent-skilledited, first seen Oct 15, 2026
- avi691/linkedin-agent-skillword for word, first seen Oct 8, 2026
Other versions7 projects use a version of this.
Word for word · 3
- avi691/linkedin-agent-skill★ 5100% same
- mubaid/dsh-linkedin-agent★ 0100% same
- robbiehaynes/job-search★ 0100% same
Edited · 3
- nessalazne/linkedin-agent-skill★ 396% same
- postzen-dev/linkedin-agent-skill★ 369% same
- furkanbilalakyuz/linkedin-agent-skill-tr★ 079% same
Wrote their own version · 1
- HemanthMChakravarthy/linkedin-agent-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- li-auditSkill
- li-carouselSkill
- li-commentSkill
- li-dmSkill
- li-humanSkill
- li-inboxSkill
- li-planSkill
- li-postSkill
- li-profileSkill
- li-replySkill
The file
We split this skill into the rules it gives an agent
1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 70
Do not dump four finished posts at once - they will all sound the same, and the user will edit none of them.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

