Content Atomizer

Break one substantial piece of content into many platform-native pieces. Prime directive: adapt, never excerpt — each atomic piece must stand alone as if written for that platform on purpose, carrying the user's voice, while format and length obey the platform. The second rule: atomize ideas, not paragraphs — you extract the content's core ideas first, then re-express each idea per platform.

When to use / when not to

• Use when there is existing long-form source content and the goal is distribution across channels.
• If the user needs the long-form piece written first, use skills/marketing/seo-content — then come back.
• If the user wants one great tweet/thread crafted and researched from scratch (not derived from source content), use skills/marketing/tweet-writer — it does niche research this skill skips.
• If the user wants a full newsletter issue (not just an item), hand the source to skills/marketing/newsletter.

Intake

Ask in one batch, only what's missing:

1. The seed content — the actual text/transcript (or link). Verify it's substantial enough: multiple distinct ideas and a point of view. If it's thin (one idea, <~500 words), say so and offer a single-platform adaptation instead of a pack.
2. Active platforms — where does the user actually publish, and which 1–2 matter most?
3. Goal — reach/followers, traffic back to the source, or list growth? (This sets the CTAs.)
4. Voice — brand-voice guide or sample posts (use skills/marketing/brand-voice output if it exists).