Podcast Pipeline
ericosiu/ai-marketing-skills
Podcast-to-Everything content pipeline. An agent skill from ericosiu/ai-marketing-skills.
Cross-format content adaptation. An agent skill from rampstackco/claude-skills.
$ npx skills add rampstackco/claude-skills --skill content-repurposing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rampstackco/claude-skills content-repurposing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-repurposing .claude/skills/content-repurposing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-repurposing" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-repurposing into .claude/skills/content-repurposing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-repurposing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rampstackco/claude-skills/tree/main/skills/content-repurposingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rampstackco/claude-skills --skill content-repurposing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rampstackco/claude-skills content-repurposing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-repurposing .agents/skills/content-repurposing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-repurposing" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-repurposing into .agents/skills/content-repurposing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-repurposing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rampstackco/claude-skills --skill content-repurposing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rampstackco/claude-skills content-repurposing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-repurposing .cursor/skills/content-repurposing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-repurposing" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-repurposing into .cursor/skills/content-repurposing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-repurposing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rampstackco/claude-skills.git --path skills/content-repurposing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rampstackco/claude-skills --skill content-repurposing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rampstackco/claude-skills content-repurposing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-repurposing .gemini/skills/content-repurposing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-repurposing" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-repurposing into .gemini/skills/content-repurposing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-repurposing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rampstackco/claude-skills content-repurposingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rampstackco/claude-skills --skill content-repurposing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-repurposing .github/skills/content-repurposing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-repurposing" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-repurposing into .github/skills/content-repurposing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-repurposing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rampstackco/claude-skills --skill content-repurposing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rampstackco/claude-skills content-repurposing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-repurposing .opencode/skills/content-repurposing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-repurposing" agent skill from https://github.com/rampstackco/claude-skills/tree/main/skills/content-repurposing into .opencode/skills/content-repurposing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-repurposing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
content-repurposingCross-format content adaptation. An agent skill from rampstackco/claude-skills.
Content Repurposing is an agent skill from rampstackco/claude-skills. Cross-format content adaptation. Turning one substantial piece into many derivative formats (blog series, email sequences, social posts, webinars, podcasts, video shorts) without losing the original's value or producing AI-slop variants. The discipline of adaptation per medium rather than mass-blast distribution. Triggers on content repurposing, content adaptation, cross-format content, content atomization, content multiplication, content distribution across formats, source-piece-to-derivative, video shorts from…
Its SKILL.md is about 6.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `README.md`, `references/aeo-extraction-patterns.md` and `references/common-repurposing-failures.md`).
It sits in Writing & Content, covering Content repurposing and Podcasting. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.
12 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Content Repurposing loads about 6.1k tokens when it runs, and up to ~31k if it reads all its reference files. Until then it costs about 220 tokens; SKILL.md has 2,999 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 2,999 words, ~6,071 tokens.
.claude/skills/content-repurposing/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.A senior editorial leader's playbook for cross-format content adaptation. The discipline of turning one substantial piece into many derivative formats without losing the original's value or producing slop variants.
Most content programs underspend on repurposing. A flagship piece costs 40-80 hours to produce; the program publishes it once, shares it on three channels, and moves on. The same piece could have produced a blog series, an email sequence, a webinar, a podcast episode, a dozen social posts, video shorts, and FAQ extractions for AI search visibility. The work to extend the source piece across formats is small relative to the value extracted; programs that skip repurposing leave most of the value unrealized.
The failure mode in the other direction is mass-blast: the same content reposted across channels without adaptation. A blog post pasted into LinkedIn as a long-text post; the email newsletter is the blog's first three paragraphs with "read more" tacked on; the YouTube video is a slideshow of the article text read aloud. Mass-blast respects neither the medium nor the audience. AI-assisted repurposing has made mass-blast cheap; the result is a wave of derivative content that performs poorly across every channel because it was adapted to none of them.
This skill is the discipline of adaptation per medium. Each format has constraints, conventions, and reader expectations the source piece does not have. Repurposing that respects those constraints produces work that earns engagement on the new format; repurposing that ignores them produces filler.
When to use this skill: planning the extension of a flagship piece across formats, auditing a repurposing pipeline that is producing low-engagement derivatives, calibrating an AI-assisted repurposing workflow that is producing slop, or designing the cross-format adaptation conventions for a content program.
This skill spans cross-format adaptation work after a source piece has been produced. The content suite distinction:
content-strategy decides what to produce.pillar-content-architecture designs the topical hub.content-brief-authoring briefs each piece.content-and-copy writes the original piece in any single format.content-repurposing (this skill) turns one piece INTO many formats.content-distribution gets content TO audiences via channels.editorial-qa verifies pre-publish, including derivatives.ai-content-collaboration is the workflow layer; AI participation rules apply within repurposing.The distinction from content-distribution is load-bearing. Distribution is channel work: getting content to audiences via the right channels. Repurposing is transformation work: turning one piece INTO many formats, each adapted for its medium. They compose: repurpose first, then distribute the right format on the right channel.
The audience: editorial leads, content directors, content ops managers, in-house teams running multi-format programs, agencies producing derivative content for clients, anyone planning to extend a flagship piece across formats.
What is not in scope: the original piece's production (covered by content-and-copy and the long-form skills), the channels themselves (covered by content-distribution), the editorial QA on derivatives (covered by editorial-qa).
The keystone framing.
One-and-done. Publish once on the source format; never reuse. The piece took 60 hours to produce; it generates traffic for 90 days; it gets shared three times; it goes silent. The team treats publication as the end of the piece's life. Output: most of the source piece's value goes unrealized; the team is always producing new flagship work because old flagship work is not being extended.
Mass-blast. Same content reposted across channels without adaptation. Blog post text pasted into LinkedIn as a long post. Email newsletter is the blog's first three paragraphs. The YouTube version is a slideshow of the text read by AI voice. Output: low engagement on every channel because nothing was adapted to any channel's conventions. Audiences perceive the cross-channel sameness as low-effort filler. AI-assisted repurposing has made this pattern cheap and common.
Adapt-by-format. Per-medium adaptation that respects each format's constraints and conventions. The blog series breaks the source piece into chapters with new ledes and closings per chapter. The email sequence builds on the source's framework with sender-voice adjustments. Social posts use platform-native conventions. The webinar adds Q&A and live elements. Output: each derivative earns engagement on its medium because it was made for that medium; the source piece's value compounds across formats.
The litmus test. Read each derivative as if you had not seen the source piece. Does it stand on its own? Does it use the medium's conventions? Would it earn engagement if it were the only thing the audience saw of this work? If yes to all three, the adaptation succeeded. If the derivative reads as "I should have read the original instead," the adaptation failed.
Not every piece is worth repurposing. Selection is the first discipline.
Strong source-piece characteristics.
Weak source-piece characteristics.
The selection audit. Run candidate pieces through these questions before committing to repurposing. Pieces that fail the audit may still be valuable but as one-and-done; programs that try to repurpose unsuitable pieces produce derivatives that feel forced.
Detail in references/source-piece-selection-criteria.md.
Eight common source-to-derivative adaptations with worked examples.
Long-form to blog series. A 6,000-word whitepaper becomes 4-6 standalone blog posts, each developing one of the whitepaper's sub-arguments with new ledes and closings.
Blog post to email sequence. A 1,500-word blog post on a multi-step framework becomes a 5-email sequence, one email per step, with sender-voice adaptation and per-email engagement hooks.
Whitepaper to webinar. Substantive whitepaper becomes a 30-45 minute webinar with the whitepaper's framework as the spine, plus live Q&A, plus interactive elements that print do not support.
Long-form to social posts. Pull-quote-style posts, framework summaries, key-question posts, contrarian-claim posts. Each social post is one moment from the source, framed for the platform's conventions.
Article to podcast episode. Article becomes the episode's spine; the host adds context, examples, and conversational elaboration; sometimes a guest interview drives the episode while the article is the show notes.
Long-form to video shorts. 60-90 second video clips on individual claims, examples, or framework elements from the source. Each short is a standalone unit; series-of-shorts can extend the source over weeks of social posting.
Research report to FAQ extractions. Specific Q&A extractions from the source piece, formatted for AI search citation and snippet capture.
Multi-piece source to ebook. Several related pieces (blog posts, articles, even social threads) consolidated into an ebook, with new connective tissue, an introduction that frames the body, and a conclusion that synthesizes.
Detail in references/format-adaptation-patterns.md.
Each medium demands and forbids specific things. Repurposing that ignores the constraints produces derivatives that fail the medium.
Email.
Social posts (text-driven platforms).
Video (long-form).
Video (short-form).
Podcast.
Webinar.
Detail in references/per-format-constraints.md.
The source piece's voice anchors the derivatives. The discipline is staying recognizable through the format shifts.
What stays constant.
What adapts per format.
The voice audit per derivative. Read or watch the derivative. Does it sound like the brand? Could a reader who knows the source piece tell the derivative is from the same source? If voice has drifted to AI-default or to the platform's default register, the adaptation lost the voice.
The AI-repurposing voice problem. AI-assisted repurposing is particularly prone to voice drift. The source piece may have specific voice characteristics; AI generation of derivatives without strong voice prompts produces derivatives that sound more generic than the source. See ai-content-collaboration for the voice-preservation discipline that applies to repurposing workflows.
Detail in references/voice-consistency-across-formats.md.
When to release derivatives relative to the source, and at what pace.
Sequencing patterns.
Cadence within the rollout.
The pacing audit. Match cadence to the source's traffic curve. Pieces with sharp early traffic (trending topics) benefit from concentrated rollout; pieces with sustained evergreen traffic can support distributed rollout over many months.
Detail in references/sequencing-and-cadence-patterns.md.
Derivatives that link to each other and to the source compound. Derivatives that ship in isolation underperform.
Linking patterns.
Attribution within derivatives. When a derivative is clearly drawn from a source piece, acknowledge: "This is adapted from our recent piece on X." Attribution earns reader trust; uncredited derivatives can feel like the same work being recycled without acknowledgment.
Co-promotion across channels. A blog post derivative can be re-shared on social where the original blog post was; a social post derivative can be promoted in the email newsletter. Cross-channel flow extends each derivative's reach.
Detail in references/cross-promotion-patterns.md.
A specific repurposing pattern worth its own treatment.
FAQ extraction. Pull specific question-answer pairs from the source piece. Each Q&A is 40-80 words. Format as standalone FAQ entries that can be cited by AI search engines.
Snippet design. Identify standalone paragraphs in the source that answer specific queries cleanly. These paragraphs can be quoted, schema-marked, and presented in derivative pieces or in dedicated FAQ pages.
Statistic extractions. AI engines weight statistics with named sources. Extract specific stats from the source (with citations to the underlying primary research) into format that AI can cite cleanly.
Definition and entity extractions. Source pieces often define specific terms or describe specific entities authoritatively. Extract these as standalone definitions in glossaries, FAQ pages, or knowledge-base entries.
The AI-search-derivative discipline. Treat AI-search optimization as a derivative format with its own conventions: specific question framings, named-source citations, standalone-paragraph design. Pieces that do this well earn AI citations; pieces that do not still get cited but at lower rates and with less control over framing.
Detail in references/aeo-extraction-patterns.md.
Rapid-fire. Diagnoses in references/common-repurposing-failures.md.
When designing or auditing a repurposing program, walk these 12 considerations.
The output of the framework is a repurposing program that turns each strong source piece into a coherent multi-format extension, with each derivative earning engagement on its medium.
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
references/source-piece-selection-criteria.md - Strong vs weak source-piece characteristics. The selection audit. Pieces that should stay one-and-done.references/format-adaptation-patterns.md - Eight source-to-derivative adaptations with worked examples. Long-form to blog series, blog to email, whitepaper to webinar, etc.references/per-format-constraints.md - What each medium demands and forbids. Email, social, video, podcast, webinar, AI search. Length norms, conventions, hooks.references/voice-consistency-across-formats.md - What stays constant and what adapts. The voice audit per derivative. The AI-repurposing voice problem.references/sequencing-and-cadence-patterns.md - Source-first vs simultaneous vs derivative-first. Concentrated vs distributed cadence. Pacing audits.references/cross-promotion-patterns.md - Linking patterns, attribution, co-promotion across channels.references/aeo-extraction-patterns.md - FAQ extraction, snippet design, statistic extractions, entity extractions for AI search citation.references/repurposing-pipeline-templates.md - Workflow templates by source-piece type. Whitepaper pipeline, blog post pipeline, research report pipeline, multi-piece consolidation pipeline.references/common-repurposing-failures.md - 11+ failure patterns with diagnoses and fixes.Repurposing is widely treated as a content multiplication problem to be solved with AI: feed the source into a tool, get derivatives out. The output of that approach is mass-blast, slop, and audiences that learn to ignore the program. The teams producing repurposing that earns engagement are the ones treating each derivative as a piece in its own right, adapted for its medium, written with the source's voice but the format's craft.
Adaptation is craft, not duplication. The source piece is the starting material; the derivative is its own work. Programs that hold this discipline get value compounding across formats; programs that skip it produce a wall of derivative content that performs worse, not better, than publishing only the source.
When in doubt about whether a repurposing program is ready, ask: does each derivative respect its medium's conventions, does voice stay consistent across the set, are derivatives cross-promoting and linking back to the source, is AI-search extraction part of the plan, is cannibalization being managed, is the cadence pacing earning engagement? If yes to all of those, the program is real. If no to any, the gap is where the derivatives will read as filler and audiences will tune out.
© rampstackco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 10 other files (references) in skills/content-repurposing of rampstackco/claude-skills.
Open the folder on GitHubat commit 482c9bf
Content Repurposing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Repurposing this skillrampstackco/claude-skills | 940 | — | ~6.1k | Automated safety check: Pass | MIT | |
| Podcast Pipelineericosiu/ai-marketing-skills | 3.6k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Ig RepurposeJakeschincariol/instagram-agent-skill | 615 | — | ~853 | Automated safety check: Pass | MIT | |
| Podcast Content SuiteOneWave-AI/claude-skills | 323 | 1 repos | ~500 | Automated safety check: Pass | MIT | |
| Youtube Downloaderguia-matthieu/clawfu-skills | 150 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Podcast Generationbytedance/deer-flow | 83k | 2 repos | ~2.2k | Automated safety check: Pass | MIT |
ericosiu/ai-marketing-skills
Podcast-to-Everything content pipeline. An agent skill from ericosiu/ai-marketing-skills.
Jakeschincariol/instagram-agent-skill
Turn one long asset - a YouTube video, podcast, livestream, newsletter, blog post or client call - into a week of reels and carousels.
OneWave-AI/claude-skills
Transform podcast transcripts into comprehensive content marketing suites including blog posts, social media content, newsletters, SEO-optimized articles, and timestamps.
guia-matthieu/clawfu-skills
Download and process YouTube content for research. An agent skill from guia-matthieu/clawfu-skills.
bytedance/deer-flow
Turns written content into a two-host conversational podcast MP3 with a transcript, by drafting a JSON script and running a text-to-speech script.
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
rampstackco/claude-skills
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.
rampstackco/claude-skills
Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.
rampstackco/claude-skills
Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.
rampstackco/claude-skills
Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.
rampstackco/claude-skills
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.
Categories
Cross-format content adaptation. An agent skill from rampstackco/claude-skills. Content Repurposing is an agent skill from rampstackco/claude-skills. Cross-format content adaptation.
Content Repurposing fits situations like: content repurposing; content adaptation; cross-format content; content atomization.
Run `npx skills add rampstackco/claude-skills --skill content-repurposing -a claude-code`. Or copy the skill folder (skills/content-repurposing in rampstackco/claude-skills) into .claude/skills/content-repurposing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rampstackco/claude-skills --skill content-repurposing -a codex`. Or copy the skill folder (skills/content-repurposing in rampstackco/claude-skills) into .agents/skills/content-repurposing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill content-repurposing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-repurposing, .gemini/skills/content-repurposing, .github/skills/content-repurposing and .opencode/skills/content-repurposing in your project.
SKILL.md names no scripts, command-line tools or credentials: Content Repurposing is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Content Repurposing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.1k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 25k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Content Repurposing: Podcast Pipeline (ericosiu/ai-marketing-skills, 3.6k stars), Ig Repurpose (Jakeschincariol/instagram-agent-skill, 615 stars), Podcast Content Suite (OneWave-AI/claude-skills, 323 stars) and Youtube Downloader (guia-matthieu/clawfu-skills, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 940 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.
Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.