li-repurpose — Claude Code skill for LinkedIn posts
li-repurpose turns a video, article, newsletter, or transcript into a week-long LinkedIn post plan. Use it to find standalone post ideas in long-form material.
MIT ★ 3,812 updated 2026-09-17
/plugin marketplace add Jakeschincariol/linkedin-agent-skill
/plugin install linkedin-agent@linkedin-agent-skillWhat li-repurpose does
The skill scans a source for claims, figures, stories, explanations, mistakes, and quotable lines. It lists the finds by category before drafting. When it finds fewer than four items, it warns that stretching them into a week of posts may produce thin results.
It then schedules the strongest claim first, places a story midweek, and saves a mechanism-focused post for later. Each post gets a different hook formula from li-post/hooks.json. Drafts come one at a time, on request, through /li-post and /li-human.
For a YouTube URL, the session needs a transcript tool; otherwise, paste in the text. In Claude Code, install through the marketplace with two commands, or use npx skills as a separate method.
What it helps with
- turn a long video or article into standalone LinkedIn post ideas
- sort post topics into a week-long schedule
- pull claims, stories, and figures from a transcript
- draft one post from a selected idea
Example prompts for the agent
- Turn this transcript into a week of LinkedIn post ideas.
- Pull standalone post topics from this article and list what you found by category.
- Draft a post from the idea I picked for Tuesday.
How to install li-repurpose
1Plugin marketplace
/plugin marketplace add Jakeschincariol/linkedin-agent-skill/plugin install linkedin-agent@linkedin-agent-skillThis installs the whole linkedin-agent plugin with all its skills
2Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-repurpose -a claude-code3Manually: put the files in place
~/.claude/skills/li-repurpose/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/li-repurpose/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-repurpose -a codex2Manually: put the files in place
.agents/skills/li-repurpose/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-repurpose -a cursor2Manually: put the files in place
.cursor/skills/li-repurpose/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/linkedin-agent-skill skills/li-repurpose2Manually: put the files in place
.github/skills/li-repurpose/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-repurpose -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill --path skills/li-repurposeManually: put the files in place
.devin/skills/li-repurpose/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about li-repurpose
How do I install li-repurpose in Claude Code?
Add the marketplace with /plugin marketplace add Jakeschincariol/linkedin-agent-skill, then install the plugin with /plugin install linkedin-agent@linkedin-agent-skill.
What does the li-repurpose skill do?
It finds separate post ideas in long-form content, schedules them across a week, and drafts posts one at a time when asked.
What do I need to process a YouTube URL?
A transcript tool must be available in the Claude Code session. If it isn’t, paste in the transcript text.
Source text
SKILL.md · MIT
--- 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.
© Jake Schincariol · MIT · Jakeschincariol/linkedin-agent-skill