Weekly Content Repurposer

Li repurpose

by Jakeschincariol · MIT license · ★ 1,856 on GitHub

Li repurpose cover

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",…

---
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,

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add Jakeschincariol/linkedin-agent-skill --skill li-repurpose -g -a claude-code
Claude Code (degit)npx degit Jakeschincariol/linkedin-agent-skill/skills/li-repurpose#main ~/.claude/skills/li-repurpose
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md2.7 KB
Read SKILL.md here
Jakeschincariol/main1 file shown
SKILL.md
Show the full text72 lines
li-repurpose/SKILL.md72 lines · 2.7 KB

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---
2name: li-repurpose
3description: >-
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 
12One good long asset contains four to six posts. Most people extract one and
13throw the rest away.
14 
15## Input
16 
17A transcript, an article, a newsletter, a script, a call summary. If the user
18gives a YouTube URL and there is a transcript tool available in the session,
19use it; otherwise ask them to paste the text. Read the whole thing before
20extracting anything.
21 
22## Extract, do not summarise
23 
24A summary of a video is not a post. Nobody wants the summary. Go through the
25asset 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 
36List what you found, with counts, before writing anything. If the asset yields
37fewer than four items, it is thin, and four posts squeezed out of it will be
38thin too. Say that.
39 
40## Then build the week
41 
42Each extract becomes one post, and each post has to stand completely on its
43own - the reader has not seen the video and never will. Never write "as I
44mentioned in my latest video". The post is the thing.
45 
46Assign a hook formula from `li-post/hooks.json` to each, and vary them: five
47posts from one source with the same hook shape reads as a content mill.
48 
49Order them across the week so the strongest claim goes first, the story goes
50midweek, and the mechanism post goes last, when people who liked the earlier
51ones are watching for it.
52 
53## Output
54 
55```
56SOURCE: "Why we killed discovery calls" (18 min, 3,400 words)
57 
58FOUND 4 claims, 6 numbers, 2 stories, 3 mechanisms, 1 mistake, 5 quotable lines
59 
60WEEK
61TUE #1 Contrarian Discovery calls are a tax you pay for a bad website
62WED #17 Time Anchor We got 6 hours a week back by deleting one calendar link
63THU #9 Cold Open "Can we just hop on a quick call?"
64FRI #21 Direct Value The 4-question form that replaced the call. Steal it.
65 
66Say "write Tuesday" and I will draft it.
67```
68 
69Then draft on request, one at a time, each through `/li-post` and `/li-human`.
70Do not dump four finished posts at once - they will all sound the same, and
71the user will edit none of them.
72 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 1,856
Checked
Source
Jakeschincariol/linkedin-agent-skill ↗
Creator
Jakeschincariol · 34 listings
View creator

Similar skills

See all →
SkillLong-Form Draftertimscheuerai/content-vault · by timscheueraiDraft written long-form content (newsletter issue, blog post, Substack issue) in your voice. 800-2000 words, structured intro + body + CTA, paragraph-by-paragraph not list-by-list. Pulls voice from /linkedin-copywriter's corpus (same author, same register · longer arc). Runs the brand-doc skill checklist before output. Logs the row in the Notion Content DB and (for newsletters) drafts a separate punchy subject line. Use when asked to "write a newsletter", "draft a blog post", "long-form X", "Substack issue about Y", "weekly newsletter", or "/long-form". For spoken video scripts (YouTube longs / shorts) use /youtube-script instead · the cadence is fundamentally different.★ 37 GitHub starsAgentPodcast Content Analyzerdavila7/claude-code-templates · by davila7Podcast content analysis specialist. Use PROACTIVELY for identifying viral moments, creating chapter markers, extracting SEO keywords, and scoring engagement potential from transcripts.★ 32.3k GitHub starsAgentPodcast Production Editordavila7/claude-code-templates · by davila7Podcast editing and post-production specialist. Use PROACTIVELY for audio editing guidance, show notes creation, chapter markers, timestamp management, and podcast publishing workflows.★ 32.3k GitHub starsAgentPodcast Metadata Specialistdavila7/claude-code-templates · by davila7Podcast metadata and show notes specialist. Use PROACTIVELY for SEO-optimized titles, chapter markers, platform-specific descriptions, and comprehensive publishing metadata.★ 32.3k GitHub starsAgentAudio Transcriberdavila7/claude-code-templates · by davila7Audio transcription specialist. Use PROACTIVELY for extracting accurate transcripts from media files with speaker identification, timestamps, and structured output.★ 32.3k GitHub starsAgentPodcast Trend Scoutdavila7/claude-code-templates · by davila7Podcast trend analysis specialist. Use PROACTIVELY for identifying emerging tech topics, breaking developments, and timely content suggestions for podcast episodes.★ 32.3k GitHub stars

More from Jakeschincariol

SkillIG Story WriterJakeschincariol/instagram-agent-skill · by JakeschincariolWrite the day's Instagram Stories - the frame-by-frame sequence, which stickers to use where, and the one that moves people into the DMs. Use when the user says "stories", "what do I post on my story", "story sequence", poll idea", "I have nothing to story about", or wants to sell something without making a post about it.★ 6k GitHub starsSkillLinkedIn Post AuditJakeschincariol/linkedin-agent-skill · by JakeschincariolPost-mortem on what the user has already published - which posts actually worked, why, and what to stop doing. Use when the user pastes their LinkedIn analytics or past posts and asks "what's working", "why did this flop", "read my analytics", "audit my content", or wants to know what to double down on.★ 1.9k GitHub starsSkillLinkedIn Carousel BuilderJakeschincariol/linkedin-agent-skill · by JakeschincariolBuild a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload. Use when the user says carousel", "document post", "slides for LinkedIn", "turn this into a carousel", or has a list-shaped idea that would die as a text post.★ 1.9k GitHub starsSkillLinkedIn Comment WriterJakeschincariol/linkedin-agent-skill · by JakeschincariolWrite comments on other people's LinkedIn posts that read as a person with an opinion, not a bot. Use when the user pastes a post and wants a comment, says comment on this", "engage with this", "what do I say here", or wants a batch of comments for their engagement round.★ 1.9k GitHub starsSkillYouTube Channel AuditorJakeschincariol/youtube-agent-skill · by JakeschincariolAudit a YouTube channel end to end - packaging, consistency, the first fifteen seconds, and what to fix first. Use for "audit my channel", "why isn't my channel growing", "review my videos", or a pasted channel URL.★ 1.1k GitHub starsSkillYouTube Chapter WriterJakeschincariol/youtube-agent-skill · by JakeschincariolWrite YouTube chapters from a transcript, validated against YouTube's own rules so they actually render. Use for "add chapters", "timestamps", break this video into sections".★ 1.1k GitHub stars