social-repurpose
Skill0 starsChanged 4 months agoMITView on GitHub
Turn one long-form asset (blog post, essay, transcript, report) into platform-native social posts. Use whenever the user shares long content and asks to "make posts from this", "repurpose", "turn this into a thread", "LinkedIn post from my article", "content for X/Twitter", or wants to promote a piece across channels. Trigger even when they just paste an article and say "post-ify this".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- inklate/social-skillstheir own version, first seen Oct 17, 2026
- DRAZY/claude-skillstheir own version, first seen Sep 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
- inklate/social-skills★ 8same name
- DRAZY/claude-skills★ 1same 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 repository8 other files it gives its agents.
- commit-craftSkill
- inbox-triageSkill
- incident-postmortemSkill
- landing-copySkill
- meeting-to-actionsSkill
- newsletter-forgeSkill
- pr-review-guardianSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 18
If the source has no idea worth spreading, say so — don't manufacture engagement bait.
- Distinctive: line 59
Never reuse the identical sentence across platforms — re-shape it.
- Distinctive: line 61
No hashtag stuffing, no "🚨 THREAD 🧵" theatrics unless the user's brand does that.
- Distinctive: line 62
If the user names only one platform, produce only that — deeply, with 2 variants to choose from.
≈ “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
Social Repurpose
One asset, many native posts. The mistake is copy-pasting the same blurb everywhere. Each platform rewards a different shape — respect it. Extract the ideas from the source, then re-form each for its channel.
Step 1: mine the source
Pull out, before writing any post:
- The one big idea (the thing worth spreading).
- 3-5 standalone insights (each true and useful on its own, no context needed).
- 1-2 surprising data points or contrarian claims (these travel).
- A concrete example or story if present.
If the source has no idea worth spreading, say so — don't manufacture engagement bait.
Step 2: shape per platform
X / Twitter (single) — one insight, one hook line, ≤280 chars, no hashtags-as-filler. Front-load the payoff.
X / Twitter (thread) — hook tweet that promises a specific payoff → one insight per tweet → last tweet = recap + soft CTA. 5-9 tweets. Each tweet must stand alone if screenshotted.
LinkedIn — hook line, then a line break (the "see more" cutoff lives here — the first line must earn the expand). Short paragraphs, 1 idea each, a lesson or POV, light CTA/question. 1200-1600 chars. No engagement-bait ("Agree?" spam).
Instagram / carousel — slide 1 = hook, slides 2-N = one point each (≤15 words/slide), final slide = CTA. Give slide-by-slide text.
Newsletter blurb — 2-3 sentences + link, written to make opening the full piece feel worth it.
Output template
## Repurposed: <source title>
**Big idea:** <one line>
### X — single
<post>
### X — thread
1/ <hook>
2/ ...
### LinkedIn
<post, with the first line isolated>
### Instagram carousel
Slide 1: <hook>
Slide 2: ...
### Newsletter blurb
<2-3 sentences + [link]>Rules
- Never reuse the identical sentence across platforms — re-shape it.
- Match the source's actual claims; don't inflate a modest finding into a bombshell.
- No hashtag stuffing, no "🚨 THREAD 🧵" theatrics unless the user's brand does that.
- If the user names only one platform, produce only that — deeply, with 2 variants to choose from.
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.