content-repurposer
Skill1 starsChanged 5 days agoMITView on GitHub
Turn one long-form piece you paste in (an article, transcript, webinar summary, or case study) into four channel-ready derivatives, an X thread, a LinkedIn post, a newsletter section, and a short-video script, each inside its channel's length and format limits, with every claim and number carried over exactly as written and any statistic the original does not source flagged instead of repeated as fact. Use when a finished piece has to go out on several channels and the derivatives must say only what the original says.
29 other projects use a version of this.
Adopted by
Most recently taken up by
- milad-ahmd/content-repurposertheir own version, first seen Nov 1, 2026
- Insightful-Pipe/social-media-skillstheir own version, first seen Nov 1, 2026
- milad-ahmd/agent-skillstheir own version, first seen Nov 1, 2026
- irinabuht12-oss/marketing-skillstheir own version, first seen Oct 27, 2026
- ARCASSystems/FounderOStheir own version, first seen Oct 24, 2026
- njpatten/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use research-synthesizer, seo-blog-writer and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
o2alexanderfedinSkillresearch-synthesizer
Creates comprehensive synthesis documents distilling research findings into actionable insights. Activates when: creating synthesis.md files, aggregating research findings, integrating multi-source data, extracting strategic insights, or resolving conflicting information. Operates across technical, market, architecture, certification, and roadmap domains. Ensures evidence-based synthesis with full traceability to source research files.
Also in 3 projects that use this
Marine-softdrink524Skillseo-blog-writer
SEO-optimized blog post writer with expertise in keyword research, content structure, meta tags, and search engine ranking strategies. Use when creating blog posts, articles, or any content that needs to rank well on Google.
Also in 3 projects that use this
raroqueSkillyoutube-script-writer
Write a tight, retention-focused YouTube script from a topic, outline, or research brief. Use when the user asks for a video script, wants to turn notes or research into a YouTube video, needs a hook/intro rewritten, or wants to plan a video end-to-end with pacing, visual beats, and CTAs.
Also in 3 projects that use this
vivy-yiSkillcontent-calendar
Use when scheduling Xiaohongshu posts, maintaining consistent posting frequency, planning content around events or seasons, or organizing content production workflow
Also in 4 projects that use this
ncklrsSkillproposal-writer
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
Also in 4 projects that use this
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- irinabuht12-oss/marketing-skills★ 6.5ksame name
- Affitor/affiliate-skills★ 757same name
- Ootto-AI/claude-content-skills★ 417same name
- OneWave-AI/claude-skills★ 378same name
- hamzafarooq/claude-code-starter★ 145same name
- marcosmodly/marketing-skill★ 141same name
- aircrushin/promptMinder★ 117same name
- travisjneuman/.claude★ 106same name
- OpenAnalystInc/10x-Content-Expert★ 15same name
- legioncodeinc/littlebird-skills★ 8same name
19 more not listed
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 repository163 other files it gives its agents.
- agents.mdAGENTS.md
- 3d-asset-handoff-sheetSkill
- accessibility-regression-auditorSkill
- adr-writerSkill
- agent-memory-designerSkill
- agent-trajectory-evaluatorSkill
- alerting-rules-tunerSkill
- analysis-memo-writerSkill
- annotation-disagreement-ledgerSkill
- annotation-task-spec-builderSkill
- api-deprecation-plannerSkill
- api-error-contract-designerSkill
- architecture-diagram-generatorSkill
- asset-metadata-review-ledgerSkill
- auth-flow-reviewerSkill
- background-job-reliability-auditorSkill
- branch-rebaserSkill
- brand-voice-profilerSkill
- bundle-analyzerSkill
- cache-policy-designerSkill
- canary-release-plannerSkill
- caption-correction-ledgerSkill
- changelog-from-prsSkill
- chart-chooserSkill
- chunking-strategy-optimizerSkill
- circular-dependency-breakerSkill
- claude-settings-auditorSkill
- code-example-verifierSkill
- cold-email-deliverability-auditorSkill
- cold-start-optimizerSkill
- commit-splitterSkill
- competitor-teardownSkill
- component-spec-writerSkill
- connection-pool-tunerSkill
- contract-obligation-registerSkill
- contract-test-designerSkill
- conventional-commitsSkill
- cors-configuratorSkill
- coverage-gap-finderSkill
- crm-export-auditorSkill
- dashboard-designerSkill
- data-retention-auditorSkill
- dataset-first-lookSkill
- dead-code-finderSkill
- deadlock-diagnoserSkill
- decision-log-reconcilerSkill
- dependency-auditSkill
- dependency-upgrade-plannerSkill
- design-brief-writerSkill
- design-critique-checklistSkill
- design-token-extractorSkill
- devcontainer-designerSkill
- distributed-tracing-instrumenterSkill
- dockerfile-optimizerSkill
- email-sequence-drafterSkill
- embedding-index-tunerSkill
- embedding-set-inspectorSkill
- entity-match-candidate-ledgerSkill
- exit-ticket-builderSkill
- extract-moduleSkill
- The first 60 shown.
The file
Files
Repurposing is where accurate long-form content turns into inaccurate short-form content: a number gets rounded, a hedge gets dropped, a "some customers" becomes "customers", and a stat that was already unsourced in the original travels to four more places. This skill treats the source as the only permitted material. It inventories every claim first, writes each derivative from that inventory, and then checks the derivatives back against it. It needs only pasted text, so it runs the same on claude.ai, in Claude Code, and in Claude Cowork; in a Claude Code project, /repurpose runs it on a file and writes the outputs to disk.
When to use this skill
- A blog post, report, or case study is published and the same idea needs to reach social, email, and video this week.
- A webinar or podcast transcript exists and you want the derivatives to quote what was actually said.
- Someone else wrote the piece and you need channel versions that do not drift from it.
- A piece is being reused months later and you need to know which of its numbers still have a source.
[!NOTE] The skill adds nothing to the source: no new examples, no rounded numbers, no stronger adjectives, no context it happens to know. If the original says "most of the teams we surveyed", the thread says that too, not "most teams". Hooks, calls to action, and closing lines the source lacks are written so they make no factual claim. Voice comes from a pasted brand-voice-profiler rules block if you supply one, otherwise from the source's own register.
Instructions
- Read the whole source and build the claims ledger. One row per factual claim, number, quotation, and named entity: the text as written, where it appears, and SOURCED (with the citation) or UNSOURCED. The ledger is the only material the derivatives may use.
- Pick the spine. One sentence the reader should remember, and three to five supporting points, each pointing at ledger rows. Every derivative is built from the same spine so the channels agree with each other.
- Write the X thread. Five to nine posts, each under 280 characters (or the limit the user states), with the character count printed after each post. The first post stands alone and makes a claim from the ledger, not a tease. Numbers appear exactly as in the source. The last post carries
[LINK]and at most two hashtags. - Write the LinkedIn post. 150 to 300 words. The first two lines carry the point, because feeds truncate the rest; short paragraphs; no more than one question; one call to action at the end. No engagement-bait openers.
- Write the newsletter section. A subhead, one paragraph of context in the second person, two or three bullets from the supporting points, and one
[LINK]. 120 to 200 words, ready to drop into an existing issue. - Write the short-video script. 45 to 60 seconds of speech, about 110 to 150 words, as a three-column table: time, spoken line, on-screen text. The hook lands inside the first three seconds and is a ledger claim, not a question. Mark any place a visual would need a number as
[SHOW: figure from ledger row N]. - Flag unsourced statistics. Any UNSOURCED number that appears in a derivative gets an inline
[UNSOURCED]marker and a row in a closing list, so the owner can source or cut it. Superlatives from the source ("the fastest", "the only") are flagged the same way. - Check the derivatives against the ledger. Compare every number, name, and quotation in the four outputs to the ledger. Nothing may be rounded, strengthened, or new. Fix drift before returning and note what was fixed.
- Assemble in this order: Claims ledger, Spine, X thread, LinkedIn post, Newsletter section, Video script, Flags, Checks applied.
Output
One Markdown document with the eight sections above. The four derivatives are ready to paste into their channels once the Flags list is cleared; the ledger stays with the document as the record of what the piece claims and what backs it. The video script can go to an editing tool such as Descript; the written derivatives can go to the content-editor agent for a voice and claims pass.
Example
Excerpt from repurposing a 1,800-word post about onboarding email timing:
### Claims ledger
| # | Claim | Location | Status |
| --- | --- | --- | --- |
| 3 | "teams that sent the second email within 24 hours saw higher activation" | para 4 | UNSOURCED (no study or internal data cited) |
| 4 | "we moved our own second email from day 3 to day 1" | para 6 | SOURCED (first-hand) |
### X thread
1/ We moved our second onboarding email from day 3 to day 1. Here is what changed and what did not. (96)
2/ The claim you will read everywhere: send it within 24 hours and activation goes up. [UNSOURCED] We could not find the study behind it. (134)
### Flags
- Ledger row 3 appears in thread post 2 and the newsletter bullet 1. Source it or cut it.The ledger discipline exists to prevent what the AI slop glossary entry describes; Claude skills for marketers shows where repurposing sits in the full set.
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.

