social-repurpose
Skill8 starsChanged 4 months agoMITView on GitHub
Mine one long-form source — a blog post, video transcript, podcast episode, or talk — for its strongest atomic ideas and turn it into a full week of platform-shaped drafts for LinkedIn, X (Twitter), and Instagram, plus a short-video script. Use when someone says "repurpose this", "turn my blog into a week of posts", "slice this video into content", or "get a week of content from this". The output is a 7-day plan: two LinkedIn posts from different angles, one X thread, three single X posts, an Instagram carousel outline, and a short-video beat sheet — each standing alone with no "as I wrote in my blog" self-reference. For the same message posted across platforms at once, use social-crosspost instead. Reads social-context.md for brand voice and audience setup so every piece sounds like the author, not a summarizer.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- DRAZY/claude-skillstheir own version, first seen Sep 14, 2026
- moses607/skillforgetheir own version, first seen Jul 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- DRAZY/claude-skills★ 1same name
- moses607/skillforge★ 0same 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- idkSkill
- social-adSkill
- social-auditSkill
- social-calendarSkill
- social-carouselSkill
- social-checkSkill
- social-contextSkill
- social-crosspostSkill
- social-hookSkill
- social-postSkill
- social-replySkill
- social-threadSkill
- social-voiceSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Read social-context.md (also check .agents/social-context.md) before mining.
- Very specific: line 36
If the file is missing, offer to run the social-context skill first — but do not block.
- Distinctive: line 40
Ingest the full source: Read the whole transcript or post, not the intro.
- Distinctive: line 59
Never place two pieces derived from the same idea on adjacent days.
- Distinctive: line 60
Keep the carousel and the video on different days so the heavier formats do not stack.
- Distinctive: line 75
Every draft carries its own context — a reader who never saw the source loses nothing.
- Distinctive: line 77
If the source is thin, deliver a smaller honest week over a padded full one, and say why.
≈ “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
Given one long-form source, extract 5–8 atomic ideas, match each to the format it is strongest in, draft everything, and lay it out as a 7-day content plan.
Context
Read social-context.md (also check .agents/social-context.md) before mining. You need:
- Brand voice: register, person, how spiky the takes are allowed to be
- Audience: what they already know, so drafts do not re-explain basics
## Platforms: which platforms matter, to weight the format mix- Content pillars, if present — ideas that fit a pillar get priority when you must cut
- The Never list: screen mined ideas against it before drafting — spiky mining is exactly what crosses red lines
If the file is missing, offer to run the social-context skill first — but do not block. Ask two or three quick questions inline (Which platforms matter most? Who is the audience? Personal or company voice?) and proceed.
Workflow
- Ingest the full source. Read the whole transcript or post, not the intro. In transcripts, the best material hides in asides, tangents, and answers to the second-to-last question — the parts the author did not know were good.
- Mine 5–8 distinct atomic ideas. Hunt specifically for: quotable one-liners, hard numbers and results, contrarian moments (where the author disagrees with common advice), stories with a turn, and step-by-step fragments that stand alone. Log each as one sentence plus the source excerpt that backs it.
- Deduplicate ruthlessly. Two ideas that would produce the same hook are one idea. If you cannot find five genuinely distinct ideas, say so and deliver fewer, stronger pieces rather than padding.
- Map ideas to formats by strength, not availability:
- Story with a turn → LinkedIn post (LinkedIn rewards narrative + lesson)
- Hard number or surprising result → single X post (the number is the hook)
- Step-by-step or list fragment → Instagram carousel or X thread
- Contrarian take → LinkedIn post or X post, wherever the audience holds the belief being attacked
- Visual or demonstrable moment → short-video beat sheet
- Draft the standard week's mix, adjusted to the platforms in social-context:
- 2 LinkedIn posts from different angles — never two takes on the same idea; each with a fold-surviving hook line and one lesson.
- 1 X thread — 3–7 tweets, first tweet works alone, strongest material in the back half.
- 3 single X posts — each built on one number, quote, or take; no hashtags.
- 1 Instagram carousel outline — cover hook + 6–8 one-idea slides + recap + CTA, slide text ≤25 words.
- 1 short-video script beat sheet — hook ≤3 seconds, 3–5 beats, spoken-word phrasing, on-screen text cues, ≤60 seconds total.
- Make every piece stand alone. No "as I wrote in my blog", no "in this week's episode", no numbering that implies a series. Each draft is written as if the idea occurred to the author this morning. Full context lives inside the draft.
- Run a voice pass. Repurposed content drifts toward summary-voice — flat, third-person, hedged. Rewrite anything that reads like a book report until it sounds like the person in social-context talking. First-person specifics ("we shipped", "I was wrong") are the tell that it worked. Check every quote against the source: verbatim or clearly paraphrased, never a misattributed punch-up.
- Spread the week. Assign each piece a day:
- Lead Monday with the strongest LinkedIn post; put the X thread mid-week when feeds are busiest.
- Never place two pieces derived from the same idea on adjacent days.
- Keep the carousel and the video on different days so the heavier formats do not stack.
- Vary platform day to day — three consecutive X days starves the other channels.
- Sanity-check coverage and constraints. Every atomic idea from step 2 is either used exactly once or explicitly parked in a leftovers list. No idea is used twice in the same week, and no draft exists that does not trace back to a mined idea. Then check each draft against its row in the Quality bar and fix any that misses its format constraint.
Quality bar
| Format | Constraint |
| LinkedIn post | Hook survives the ~200-char fold; ≤1,300 chars preferred; one lesson each |
| X thread | 3–7 tweets; tweet 1 stands alone; each tweet ≤280, one idea per tweet |
| Single X post | ≤280; the number or the take is the hook; no hashtags |
| Instagram carousel | Cover ≤8 words; 6–8 content slides, ≤25 words each; recap + CTA |
| Short-video beat sheet | Hook ≤3 seconds; ≤60 seconds total; written for the mouth, not the page |
- The two LinkedIn posts must attack different ideas, not restate one.
- Every draft carries its own context — a reader who never saw the source loses nothing.
- Quotes from the source must be verbatim or clearly paraphrased, never misattributed punch-ups.
- If the source is thin, deliver a smaller honest week over a padded full one, and say why.
Deliverable
Return, in order:
- The mined idea list — one line per idea with the source excerpt that backs it.
- The drafts, grouped by format, each ready to copy.
- A 7-day markdown schedule table with columns Day, Platform, Format, Hook (first line).
- A leftovers list of unused ideas worth a future week.
Nothing else — end there.
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.

