AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Repurpose Planner

skill-imtaegan-claude-ugc-skills-repurpose-planner · by ImTaegan

Turn one piece of long-form content into platform-specific repurposing plans (TikTok, IG carousel, LinkedIn, X thread, YouTube short, newsletter). Each output has a unique angle for that platform, not just a reformatted clip.

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-imtaegan-claude-ugc-skills-repurpose-planner

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-imtaegan-claude-ugc-skills-repurpose-planner)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Repurpose Planner? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Repurpose Planner

Most "repurposing" is dropping the same content on every platform. That doesn't work — each platform's audience wants something different. This skill generates platform-native plans, each with its own angle.

Instructions for Claude

Step 1: Get the Source Content

Ask the user for ONE of:

  1. Paste the content directly (transcript, article, post)
  2. Summarize it in 5–10 sentences (the user's choice)
  3. Path to a file in the project directory (transcript, doc)

If the user describes the content vaguely ("my new video about productivity"), push for the actual content — you can't repurpose what you can't read.

Step 2: Identify the Core Insight

Read the source. Extract:

  • The single most quotable sentence (the line that, on its own, would stop a scroll)
  • The strongest 1–2 specific moments (a number, a story, a result)
  • The 3–5 distinct ideas within the source
  • Who the source was originally for (audience hint from the framing)

Display this back to the user briefly:

## Source content — what I'm working with

**The single most quotable line**: "[line]"
**Strongest moments**: [list]
**Distinct ideas inside**: [list]
**Original audience**: [audience]

Confirm this before I plan? Type "go" or correct anything off.

Step 3: Pick Target Platforms

Ask:

Which platforms should I plan for? (Pick any combination.)
- TikTok / IG Reels short (60s vertical)
- IG carousel (5–10 slides)
- LinkedIn post (long-form text)
- X / Twitter thread (5–9 tweets)
- YouTube Shorts (60s vertical, slightly different from TikTok)
- Newsletter section (200–400 words)

Default: all of them. Type a list to narrow.

Step 4: Generate Platform-Specific Plans

For EACH selected platform, generate a plan using the conventions below. Critically: each plan must have a unique angle. The same content, framed differently per audience.


TikTok / IG Reels short
## TikTok / IG Reel — 60s

**Angle for this platform**: [what the TikTok audience cares about]
**Pulled from source**: [which moment / idea]

**New hook (re-edited)**: "[hook]"
**Shot list**:
1. [Shot] — [purpose]
2. [Shot] — [purpose]

**Spoken script** (approx 60s):
[Full script with timing — this is mostly a re-cut of the source, but with a new hook for the algorithm]

**On-screen text key beats**:
- 0–2s: [text]
- [Nbeat]: [text]

**Caption**: [1–2 sentences max]
**Hashtags**: [3–5]

TikTok angle bias: tease + payoff, fast cuts, specific moments, less "context", more "here's the thing". Audiences scroll fast — earn the second second.


IG carousel
## IG Carousel — [N] slides

**Angle for this platform**: [why this works as a carousel — usually because it benefits from slow-pace, swipeable structure]
**Pulled from source**: [which idea]

**Slide 1 — Hook slide**
Title: "[Hook title]"
Body: [1 line]
Visual cue: [bold text / number / question]

**Slide 2 — [Section name]**
[Title and body]

[... slides ...]

**Final slide — CTA / payoff**
[Wrap with the takeaway and a soft CTA]

**Caption (long)**: [3–5 short paragraphs, expands on what the carousel doesn't fit]
**Hashtags**: [10–15]

IG carousel angle bias: educational, listicle-friendly, swipe rewards. Make slides visually scannable.


LinkedIn post
## LinkedIn post — [N] words

**Angle for this platform**: [LinkedIn audience wants opinions + lessons + stories, not videos]
**Pulled from source**: [which moment]

**Post**:

[Hook line — story open or contrarian works best]

[Empty line]

[2–4 short paragraphs — usually first-person narrative, then a takeaway, then 3–5 line spaced bullets if applicable]

[Empty line]

[Final line — often a question to invite comments, or a single-line takeaway]

**Hashtags**: [0 or 3 max — LinkedIn does NOT like hashtag stuffing]
**Best post time**: Tue/Wed/Thu morning EST is the standard recommendation.

LinkedIn angle bias: story → lesson → takeaway. First-person + specific = credibility. Don't repost a TikTok caption.


X / Twitter thread
## X thread — [N] tweets

**Angle for this platform**: [X audience wants compressed, punchy ideas — threads work when each tweet earns the next]
**Pulled from source**: [which idea]

**Tweet 1** — Hook tweet
"[Hook, ≤240 chars, often ends with a setup like 'Here's how:']"

**Tweet 2** — [section]
"[Body, ≤240 chars]"

[... continue ...]

**Final tweet** — CTA / loop-back
"[Often references the hook again, then a soft CTA like 'follow for more' or 'reply with a [thing] and I'll DM the [resource]']"

X thread angle bias: each tweet is a deliverable. No throat-clearing. Numbered or labeled tweets often outperform.


YouTube Shorts
## YouTube Short — 60s

**Angle for this platform**: [YouTube algo rewards completion + retention — Shorts hooks are slightly more "click-y" than TikTok]
**Pulled from source**: [which moment]

**Hook** (often more clickbait-y than TikTok): "[hook]"

**Beats**:
[Same structure as TikTok script but tilted toward completion — list-style content, before/after, specific countdowns work well here]

**Title**: "[≤60 chars]"
**Description**: "[2–3 sentences, hashtag-light]"
**Hashtags**: [3–5]

YouTube Shorts angle bias: clearer titles than TikTok, list/countdown formats, completion is the goal.


Newsletter section
## Newsletter — 200–400 words

**Angle for this platform**: [Subscribers chose to be there — they want depth, the parts you couldn't fit in a 60s clip]
**Pulled from source**: [which idea + which depth]

**Section title**: "[Title]"

[Opening paragraph — different from the video hook; can assume the reader wants to be there]

[Middle paragraphs — the depth the video skipped, OR the meta lesson behind the video]

[Closing paragraph — connect to a CTA: a link to the video, a tool you use, a follow-up post]

Newsletter angle bias: depth + meta. Video tells the story; newsletter tells the lesson behind the story.


Step 5: Highlight What's NOT a Repurpose

After the plans, add:

## What I deliberately didn't repurpose

[1–2 things from the source that DON'T translate well, with brief reason]

Example:
- The 3-minute technical deep-dive in the middle is too long for short-form
  and too narrow for LinkedIn. It belongs in a blog post or a longer YouTube
  video, not in any of these formats.

This signals taste and stops the user from spamming the same content blindly.

Hard Rules

  1. Each platform plan must have its own angle. If you can copy-paste the same content across platforms, you've failed. The angle line at the top of each plan must be platform-specific.
  1. Don't fabricate details from the source. If the source doesn't have a specific number, don't invent one. Use the source's actual language for quotes/moments.
  1. Honor each platform's culture:
  • TikTok: short, specific, tease + payoff
  • IG carousel: visual + listicle
  • LinkedIn: story → lesson, no hashtag spam
  • X: each tweet earns the next, compressed
  • YouTube Shorts: completion-driven, list/countdown friendly
  • Newsletter: depth + meta, hyperlink-friendly
  1. The user's original audience matters. A dev's content shouldn't be repurposed for a fashion audience. Stay near the original audience unless asked.
  1. Mention what NOT to repurpose. Section at the end. Shows judgment.

Error Handling

Source content too short to repurpose meaningfully:

This source is [N] words / sentences — too thin to repurpose into platform-
specific plans without padding. Either:
1. Send a longer source (transcript, article, post)
2. Pick fewer platforms (for a 30-word source, 1 LinkedIn post or 1 X thread
   is the realistic max)

User wants me to "just rewrite it for each platform":

Same content rewritten = the trap most repurposing tools fall into. Different
platforms want different *parts* of the source. Let me pick the part for each
platform — that's what makes it work.

Integration with Other Skills

  • Captions: After repurposing, use /caption-pack for tighter platform-specific captions on the actual posts
  • Voice: Apply /brand-voice to make all outputs match a saved profile

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.