---
description: Repurposes an existing post across platforms with full voice recalibration -- not copy-paste. Substack-long → LinkedIn excerpt+link, or LinkedIn → Substack short newsletter. Reads source post, extracts the sharpest standalone claim, redrafts in target platform's voice. Tier 3 main session. Triggered by 'repurpose POST-NNNNN', '/repurpose [POST-NNNNN] [target-platform]'.
---

# personal-content-repurpose

When a piece on one platform deserves to live on another. NEVER copy-paste — different platforms, different voices.

The user explicitly chose "no auto-cross-posting" — this skill is the deliberate, voice-recalibrated alternative.

## Trigger phrases

- "Repurpose POST-NNNNN"
- "Make a LinkedIn version of this Substack"
- "Make a Substack short from this LinkedIn"
- `/repurpose [POST-NNNNN] [target-platform]`

## Inputs

- The source post at `~/.personal/content-bank/drafts/POST-NNNNN.md` or `posted/POST-NNNNN.md`
- `~/.career/voice-profile.md`
- `~/.career/platform-rules.json` for the **target** platform
- `~/.career/memory/recent-posts.md`

## Common patterns

### Pattern 1 — Substack-long → LinkedIn excerpt

Most common. A Substack piece dropped; you want a LinkedIn post that pulls one sharp insight + drives traffic to the full piece.

Flow:

1. Read the Substack piece
2. Identify the **single sharpest standalone claim** (something that lands as a complete thought without the full piece's context)
3. Redraft as a LinkedIn post (120-220 words) using LinkedIn voice + format
4. End with a link back: "Full piece →[Substack URL]"
5. Run voice smell test
6. Save as new POST-MMMMM linked to source POST-NNNNN

### Pattern 2 — LinkedIn → Substack short

Occasional. A LinkedIn post got engagement; expand the thinking into a 400-700 word newsletter.

Flow:

1. Read the LinkedIn post + any captured comment threads
2. Identify what's worth expanding (counter-arguments raised, more examples, deeper context)
3. Redraft as Substack short with: original claim → expanded reasoning → 1-2 examples → close
4. NEW title + subtitle (don't reuse the LinkedIn hook)
5. Voice smell test
6. Save as new POST-MMMMM linked to source POST-NNNNN

### Pattern 3 — Substack-long → Substack-short summary

Less common but useful. After a long-form piece is published, send a short "highlights" newsletter to subscribers who skipped the long one.

Flow:

1. Read source long-form
2. 3 takeaways, each 1-2 sentences
3. "Read the full piece →"
4. Save as new POST-MMMMM

### Pattern 4 — LinkedIn → LinkedIn (different angle)

Same idea, different framing, weeks later. Useful when the original landed but is worth reinforcing.

Flow:

1. Read source post
2. Pick a different hook strategy (if original was a moment, try a sharp claim; vice versa)
3. Same insight, different opening, different structure
4. **MUST be ≥30 days after original** (recent-posts memory enforces this)

### Pattern 5 — Refused

If the user requests a repurpose and the source post is too platform-native to repurpose well, the skill REFUSES with rationale:

> "POST-NNNNN is too LinkedIn-native to repurpose to Substack — it's voice + moment without enough underlying claim to expand. Instead, would you like to capture a NEW idea inspired by what worked here?"

This is correct behavior. Repurposing should NEVER produce a flat translation.

## Process

### Stage 1 — Read source

Load the source post + its engagement metadata (if posted) + voice profile + target platform rules.

### Stage 2 — Plan recalibration (Tier 2)

Quick analysis:

- What's the central claim of the source?
- What's the source platform's voice doing here that needs to change for target?
- What's the target platform's expected length / format?
- Is there sufficient substance to repurpose, or should the skill refuse?

If insufficient substance → refuse with rationale.

### Stage 3 — Redraft (Tier 3 main)

Draft for the target platform from scratch — using the source as raw material, not as text-to-translate.

This means:

- New hook (target platform's hook patterns)
- New structure (target's format)
- New length (target's word count)
- Voice recalibrated (LinkedIn voice ≠ Substack voice even from same person)

### Stage 4 — Voice smell test

Standard battery on the new draft.

### Stage 5 — Output

```markdown
**Repurpose** of POST-NNNNN — "[source title]" → [target platform]

**Source:** [POST-NNNNN] (LinkedIn / Substack-long / Substack-short)
**Target:** [LinkedIn / Substack-long / Substack-short]
**Source words:** [N] | **Target words:** [M]

**Recalibration notes:**
- Source voice: [characteristic]
- Target voice: [characteristic]
- Sharpest standalone claim from source: "[..]"
- New hook strategy: [name]

**Voice smell test:** ✅

---

[full new draft]

---

**Saved to:** `~/.personal/content-bank/drafts/POST-MMMMM.md`
**Linked source:** POST-NNNNN

**My honest read:** [1 sentence — does this earn its existence as a separate piece, or is it filler?]

**Open question:** [if any]
```

### Stage 6 — Tracker update

New POST-MMMMM tracker item with `repurposed_from: POST-NNNNN`. Source POST-NNNNN gets `repurposed_into: [POST-MMMMM]`.

## Discipline

- **Recalibrate, don't translate.** A LinkedIn excerpt is NOT a paragraph from the Substack with a link — it's its own piece with its own voice.
- **Refuse when appropriate.** If there's no substance to repurpose, say so. Don't fill space.
- **Wait between LinkedIn → LinkedIn repurposes.** ≥30 days minimum, enforced by recent-posts check.
- **Different platforms = different audiences = different voice.** The user has different audiences on LI vs SS — respect that.

## What this skill does NOT do

- Does NOT copy-paste between platforms
- Does NOT use AI to "tweak" same content for different platforms (that's the AI-tell engine)
- Does NOT auto-trigger after every post — runs only on explicit request

## Cost

Per repurpose: ~$0.05 (Tier 3 main, short read + redraft). Occasional use, low budget impact.