yt-repurpose
Skill1 starsChanged 37 days agoMITView on GitHub
Turn one long video into the week's content everywhere else - Shorts, an X/Twitter thread, a LinkedIn post, a newsletter section and a blog outline - each rewritten for its platform, not copy-pasted. Use for "repurpose this", "turn this into a thread", "make posts from my video", "newsletter from this", or cross-posting a video.
In this repository25 other files it gives its agents.
- openai/AGENTS.mdAGENTS.md
- llms.txtllms.txt
- yt-analyticsSkill
- yt-auditSkill
- yt-briefSkill
- yt-chaptersSkill
- yt-collabSkill
- yt-commentSkill
- yt-editSkill
- yt-endscreenSkill
- yt-funnelSkill
- yt-ideaSkill
- yt-packageSkill
- yt-planSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-seriesSkill
- yt-shortsSkill
- ytSkill
- yt-sponsorSkill
- yt-thumbnailSkill
- yt-trendSkill
- yt-viralSkill
- yt-voiceSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 13
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Distinctive: line 24
Use the available voice profile or creator context (see the operating guide).
- Distinctive: line 48
Keep one link discipline: every off-platform piece points back to the video, once, without begging.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
yt-repurpose
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
One video is a week of content on every other platform - but only if it is rewritten, not pasted. A YouTube hook is not an X hook; a chapter is not a newsletter section. This does the translation.
For Shorts selections, use /youtube-agent-pro:yt-shorts to create timecoded clip plans. Neither skill cuts or renders media on its own; a separate editing tool is needed for exports.
Before you write
- Use the available voice profile or creator context (see the operating guide). The voice travels across platforms; the format does not.
- Work from the transcript, not your memory of the video. Ask for it (
.srt,.vttor pasted) if it is not here. Never invent a quote the creator did not say.
Produce only the platforms the user requested; the table is a menu, not a required bundle.
The translation table
Each platform rewards a different shape. Do not reuse the YouTube opening on any of them.
| platform | what it wants | length |
| Shorts / Reels / TikTok | one self-contained moment, new first line, loud payoff | 15-45s, hand to /youtube-agent-pro:yt-shorts |
| X / Twitter thread | the one counterintuitive claim first, then the proof, one idea per post | 5-9 posts |
| the story and the lesson, first two lines before the "...more" fold | 150-250 words | |
| Newsletter | the context the video assumed, plus the link, plus the one takeaway | one section |
| Blog / SEO | the searchable version - H2s off the chapters, the transcript cleaned into prose | outline + intro |
The move
- Pull the three load-bearing ideas from the transcript - the ones the video is actually about.
- For each platform, write the opening in that platform's shape. The opening is the whole job on every one of them, same as YouTube.
- For Shorts, pick the moments and hand off to /youtube-agent-pro:yt-shorts for the per-clip first lines.
- Keep one link discipline: every off-platform piece points back to the video, once, without begging.
What to hand back
- a thread, a LinkedIn post, a newsletter section and a blog outline, each ready to paste
- the Shorts shortlist (moments + timecodes) routed through /youtube-agent-pro:yt-shorts
- one line: which platform this particular video is strongest on, and why
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.