Content Repurposer Tool

v1.0.0

Repurpose long-form content (blog posts, articles, newsletters, YouTube transcripts) into platform-optimized social media posts, Twitter/X threads, LinkedIn...

0· 90·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for charlie-morrison/content-repurposer-tool.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Content Repurposer Tool" (charlie-morrison/content-repurposer-tool) from ClawHub.
Skill page: https://clawhub.ai/charlie-morrison/content-repurposer-tool
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install content-repurposer-tool

ClawHub CLI

Package manager switcher

npx clawhub@latest install content-repurposer-tool
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (repurpose long-form content) match the instructions: extract content from URL/YouTube/text/file, analyze, and generate platform-specific posts. No unexpected binaries, credentials, or install steps are requested.
Instruction Scope
Instructions explicitly tell the agent to fetch web content (web_fetch), optionally use a youtube-transcript skill, and read user-supplied file paths (.md, .txt, .html, .pdf). This behavior is consistent with the skill's purpose but means the agent will access remote URLs and any local file paths you provide — review carefully before giving sensitive file paths or links.
Install Mechanism
No install spec and no code files — instruction-only skill. This is the lowest-risk install model; nothing new will be written to disk by an installer.
Credentials
The skill requests no environment variables, credentials, or config paths. There are no disproportionate secret or system-access requests.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or elevated privileges. Normal autonomous invocation is allowed by platform defaults but not excessive here.
Assessment
This skill appears to do what it says: turn content (URLs, pasted text, or files you point it to) into social posts. Before using it, avoid supplying paths to sensitive local files or private URLs you don't want read. Be aware it will fetch the web URLs you give it (and may call a youtube-transcript helper if available). If you need stronger guarantees, ask the publisher for source code or run the skill in a restricted environment; otherwise it's reasonable to use for routine repurposing tasks.

Like a lobster shell, security has layers — review code before you run it.

latestvk978dfbz5a7y6h0cz7b3rdchbx84rrkj
90downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Content Repurposer

Transform any long-form content into platform-optimized outputs. Feed it a URL, text, or document — get back ready-to-post content for multiple platforms.

Workflow

1. Extract Source Content

Determine the source type and extract content:

  • URL → Use web_fetch to extract readable text
  • YouTube URL → Use youtube-transcript skill if available, otherwise web_fetch
  • Pasted text → Use directly
  • File path → Read the file (supports .md, .txt, .html, .pdf)

If extraction fails, inform the user and suggest alternatives.

2. Analyze Content

Before generating outputs, analyze the source:

  1. Core message — What is the single main takeaway?
  2. Key points — List 3-5 supporting points or insights
  3. Quotable lines — Extract 2-3 memorable phrases or statistics
  4. Target audience — Infer from tone, vocabulary, and subject matter
  5. Content type — Tutorial, opinion, news, case study, announcement, story

3. Generate Platform Outputs

Generate requested formats (default: all). Each format follows platform-specific rules from references/platform-guides.md.

Available formats:

  • Twitter/X thread — 3-10 tweets, hook-first, one idea per tweet
  • Twitter/X single post — Standalone tweet, max 280 chars
  • LinkedIn post — Professional tone, 1300 chars max, uses line breaks for readability
  • Instagram caption — Casual tone, hashtags, emoji-friendly, CTA at end
  • Email newsletter snippet — 2-3 paragraphs, subject line included
  • Short summary — 2-3 sentences, platform-agnostic
  • Reddit post — Title + body, informative tone, no self-promotion feel
  • Hacker News — Title only (concise, factual), optional top-level comment

4. Apply Tone & Style

If user specifies a tone or brand voice, apply it. Otherwise, match the source's tone but optimize for each platform's conventions.

Tone options: professional, casual, witty, authoritative, friendly, provocative, educational.

5. Output Format

Present outputs in clear sections:

## Source Analysis
- Core message: ...
- Key points: ...

## Twitter/X Thread (N tweets)
🧵 1/ [hook tweet]
2/ [supporting point]
...

## LinkedIn Post
[post content]

## Email Newsletter
Subject: ...
[body]

Customization Options

Users can specify:

  • Platforms — "just Twitter and LinkedIn"
  • Tone — "make it casual" / "keep it professional"
  • Audience — "targeting developers" / "for marketing managers"
  • Length — "keep the thread short, 3-4 tweets max"
  • CTA — "include a link to [URL]" / "ask them to subscribe"
  • Hashtags — "include hashtags" / "no hashtags"
  • Emoji — "use emojis" / "no emojis"
  • Language — generate in specified language

Platform Guides

For detailed platform-specific formatting rules, character limits, and best practices, see references/platform-guides.md.

Tips

  • When repurposing tutorials: focus on the "aha moment" or key insight, not the step-by-step
  • When repurposing news: lead with impact/consequence, not the event itself
  • When repurposing case studies: lead with the result, then the method
  • For threads: each tweet should work standalone — readers may see any single tweet
  • Always adapt vocabulary and jargon level to the target platform's audience

Comments

Loading comments...