Content Repurpose

Skill Preview

---
name: repurpose
description: Transform existing content — text, file, or URL — for a different audience, persona, channel, or format. Paste a blog post, get LinkedIn posts, email copy, and ad hooks back. No integrations required. Standalone version; for full GTM knowledge base support see github.com/octavehq/lfgtm.
---

# /repurpose - Content Repurposing

Transform existing content for a different audience, persona, channel, or format. Paste a blog post, whitepaper, transcript, or any text, and get it rewritten for whoever actually needs to read it.

**No integrations required.** You provide the source content and audience context; Claude handles the transformation.

> **Want even better output?** Connect your GTM knowledge base to pull persona definitions, brand voice guidelines, and playbook messaging automatically. See the full version at [github.com/octavehq/lfgtm](https://github.com/octavehq/lfgtm).

## Usage

```
/repurpose <source>
```

Where `<source>` is:
- **Text** — paste directly or provide in quotes
- **File** — local file path (`.md`, `.txt`, `.pdf`, `.docx`, `.html`)
- **URL** — web page or document URL

## Examples

```
/repurpose "Our platform reduces deployment time by 80%..."
/repurpose ./content/enterprise-whitepaper.md
/repurpose https://blog.company.com/our-product-launch
/repurpose --from "CTO audience" --to "CFO audience"
```

## Instructions

When the user runs `/repurpose`:

### Step 1: Capture the Source Content

**Identify source type and extract:**

- **Text provided directly** → confirm receipt and show first 200 chars with word count
- **File path** → use Read tool to load it; confirm it loaded
- **URL** → use WebFetch to extract main content; confirm what was fetched

If no source provided, ask:

```
What content would you like to repurpose?

1. Paste text directly
2. Provide a file path (e.g., ./content/blog.md)
3. Provide a URL

(Paste content, path, or URL):
```

### Step 2: Understand the Transformation

Ask in a single prompt — don't ask one question at a time:

```
Got it. Now let's define the transformation.

WHO is this for? Describe the target audience:
(e.g., "CFO at a 200-person SaaS company", "first-time developer", "non-technical executive buyer")

WHAT do you need?
1. Adjust tone/voice for a different persona
2. Change format (e.g., blog → email, whitepaper → one-pager, transcript → LinkedIn post)
3. Shift focus (e.g., technical → business value, features → outcomes)
4. Adapt for a specific channel (LinkedIn, email, ad copy, sales deck slide)
5. Condense or expand length
6. Multiple transformations at once

Which best describes what you need? (number or describe it):

ANY SPECIFIC INSTRUCTIONS? (optional)
Examples: "Focus more on ROI", "remove jargon", "add a stronger CTA", "keep the structure but swap the examples"
```

### Step 3: Confirm the Plan

Before generating, present a concise transformation plan:

```
REPURPOSING PLAN
================

Source: [Type] — [word count] words
Original audience: [Inferred from content]

Target:
- Audience: [What user described]
- Format: [Original format → target format]
- Channel: [If specified]
- Length: [Condensed / Expanded / Same]

Key Changes:
1. [e.g., "Shift from feature descriptions to business outcomes"]
2. [e.g., "Replace technical metrics with ROI / cost language"]
3. [e.g., "Add a clear CTA at the end"]
4. [e.g., "Shorten to ~300 words for email"]

Proceed, or adjust the plan?
```

Wait for confirmation before generating.

### Step 4: Generate

Generate the repurposed content directly. Apply the transformation using:
- The source content
- The audience description and transformation instructions
- Any specific guidance the user provided

If the user described an audience well, lean into their stated priorities and communication preferences (e.g., a CFO cares about cost, risk, and ROI; a developer cares about implementation, APIs, and time-to-value).

If the user requested **multiple outputs** (e.g., "turn this blog into 3 LinkedIn posts + 1 email"), generate all variants in sequence, clearly labeled.

### Step 5: Present Results

```
REPURPOSED CONTENT
==================

[Generated content]

---

CHANGES MADE
------------
✓ [Change 1 — brief description]
✓ [Change 2 — brief description]
✓ [Change 3 — brief description]

---
What would you like to do?

1. Refine further (share feedback)
2. Try a different angle or tone
3. Repurpose for another audience
4. Generate additional format variants
5. Done
```

### Step 6: Iterate

If the user wants refinements:

```
What should I adjust?

1. More [formal / casual / urgent / conversational]
2. Focus more on [topic]
3. Shorter — cut to [target word count]
4. Stronger CTA
5. Other: [describe]
```

Regenerate with updated instructions. Keep the source content in context across iterations.

## Common Transformations

### Blog → Email Sequence
Extract 3 core insights. Each becomes one email: hook from the insight, short context, one CTA. Conversational 1:1 tone throughout.

### Technical Doc → Executive Summary
Remove jargon. Lead with outcomes, not features. Add financial impact. Cut to 1 page. One metric per claim.

### Internal Brief → Customer-Facing Content
Remove internal references and assumptions. Reframe features as benefits. Add social proof where relevant. Include a CTA.

### One Persona → Another
- **Technical → Economic buyer**: swap features for outcomes, add ROI framing, simplify complexity
- **Champion → Decision Maker**: add risk mitigation, strategic framing, proof at scale
- **New audience**: match their vocabulary and what they're measured on

### Long Content → Social Posts
Pull 3–5 quotable insights. Each becomes a standalone LinkedIn post: hook → context → takeaway → optional CTA. Under 150 words each.

### Transcript → One-Pager
Extract the key narrative thread. Structure as: situation → complication → solution → result. Use their own language where possible.

## Input Handling

### Text
```
/repurpose "Your content here..."
```
Or paste in follow-up after running `/repurpose` with no argument.

### File
```
/repurpose ./path/to/content.md
```
Supported types: `.md`, `.txt`, `.html`, `.pdf`, `.docx`

### URL
```
/repurpose https://example.com/blog-post
```
Uses WebFetch to extract main content. If the page requires auth or blocks fetching, ask the user to paste the content directly.

## Error Handling

**File not found:**
> Couldn't find the file at [path]. Check the path and try again, or paste the content directly.

**URL fetch failed:**
> Couldn't fetch [URL] — the page may require login or block automated access.
> Paste the content directly instead.

**Content too long:**
> The source is [N] words — that's quite long.
> Options:
> 1. Repurpose the full content
> 2. Paste a specific section to focus on
> 3. Let me summarize first, then repurpose the summary

**No audience context:**
> I can repurpose this without audience context, but the output will be generic.
> Describe who this is for (title, company type, their priorities) and I'll tailor it much more precisely.

## Related Skills

- `/positioning` — Build the positioning system your content should reflect
- `/microsite` — Turn content into a personalized ABM landing page