# Repurpose

> Repurpose one source asset into platform-specific social media posts while preserving the original idea and adapting format, tone, and call to action. Use when turning blogs, transcripts, changelogs, podcasts, videos, demos, notes, or launch plans into a social content package.

- Skill: `agentreacher/repurpose` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add agentreacher/repurpose`
- Raw SKILL.md: https://api.skillmd.com/api/skills/agentreacher/repurpose/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: agentreacher (https://skillmd.com/u/agentreacher)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/agentreacher/repurpose

---


# Repurpose

Turn one source asset into a compact campaign package. The goal is not to summarize everywhere. The goal is to extract the strongest ideas and make each platform feel native.

## Inputs

- source asset: pasted text, URL summary, transcript, changelog, feature note, launch plan, or rough idea
- target platforms
- audience segment
- campaign goal
- brand voice constraints
- hard facts that must remain accurate
- claims to avoid

If the source is long, first extract a reusable idea inventory.

## Idea Inventory

Pull out the core promise, 3-7 atomic ideas, proof points, story moments, objections, reusable phrases, visual opportunities, and calls to action. Discard weak ideas before creating posts. Repurposing should make a campaign sharper, not larger.

## Workflow

1. Map the source into campaign angles:
   educational, founder story, product demo, objection handling, proof, and contrast.

2. Select platform formats:
   X post/thread, Instagram post/reel/carousel, Facebook post, LinkedIn narrative/list, TikTok short-form video, YouTube Short, Pinterest pin, Threads sequence, and Bluesky post.

3. Write channel-native drafts:
   give each post a distinct angle, reuse facts rather than wording, adapt CTA intensity to platform norms, and keep proof visible.

4. Build a simple schedule:
   launch/publish day, 2 follow-up posts, 1 objection-handling post, and 1 proof or demo post.

5. Add reuse notes:
   visual asset, schedule-ready status, and human approval needs.

## Quality Bar

- No generic "excited to announce" unless it is intentionally undercut by a strong second line.
- No identical cross-posting except for very short announcements.
- No inflated claims beyond the source.
- Each platform draft should make sense even if seen in isolation.
- The campaign should have sequence logic: introduce, deepen, prove, remind.

## Output Format

```md
## Source Distillation
- Core idea:
- Best proof:
- Audience tension:
- Campaign goal:
## Content Package
### X
[drafts]
### LinkedIn
[drafts]
### Short-form Video
[hook, beats, caption]
## Schedule
| Timing | Platform | Angle | Asset | Status |
| --- | --- | --- | --- | --- |
## Approval Notes
- [fact/claim needing review]
```

## AgentReacher Notes

Compatible with AgentReacher autonomous posting pipelines. Use this skill before scheduling so the campaign enters the calendar as platform-specific posts instead of duplicated copy.

Example usage in AgentReacher: "Repurpose this changelog into a one-week launch campaign for X, Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Threads, and Bluesky."

