content-repurposer git:20261011.4c5134fA

Immutable. This exact content never changes and is served at /api/v1/blob/95188a0d2a2c7b5e.

---
name: content-repurposer
description: Reframe one source into channel-ready content while preserving claims, voice, disclosure requirements, and a clear review trail.
---

# Content Repurposer

Use this skill when a source asset needs to become several useful deliverables, such as a launch note, newsletter, social post, FAQ, or sales enablement brief.

## Working contract

Ask for the source, audience, channels, goals, brand voice, forbidden claims, disclosure rules, and a final reviewer. If the source is incomplete, identify the missing fact instead of inventing a bridge sentence.

## Method

1. Extract the source’s facts, claims, proof, examples, and calls to action into a source ledger.
2. Mark each statement as safe to preserve, safe to compress, requires review, or unsupported.
3. Create a channel matrix with format, length, audience intent, and required elements.
4. Draft each asset from the ledger, preserving the source’s meaning while changing structure and emphasis.
5. Run a fact check against the source. Flag new numbers, superlatives, guarantees, and implied comparisons.
6. Run a voice check for tone, banned phrases, accessibility, and disclosure requirements.
7. Return a publishing sequence and the one review question that could still change the package.

## Output format

Return:

1. **Source ledger** with claim, evidence, and reuse status.
2. **Channel plan** with audience, format, length, and job to be done.
3. **Content package** with one clearly labeled draft per channel.
4. **Fact and claim audit** with any unsupported or newly introduced language.
5. **Publishing checklist** with reviewer, disclosure, links, and final approval.

## Quality rules

- Keep source facts traceable in every derivative.
- Never add testimonials, metrics, guarantees, or urgency the source does not support.
- Match the channel’s reading behavior without flattening the brand voice.
- Make edits easy to review by keeping each draft separate.
- If a claim cannot be checked, write it as a question or remove it.