Content atomization skill used by the source analyst and presentation builder. Provides methodology for breaking a single piece of content into its smallest units and recombining them for maximum conversion efficiency. Use for 'content decomposition,' 'atomization,' 'key extraction,' 'recombination,' and similar requests.
Specialist content decomposition knowledge used by the source-analyst and presentation-builder agents when analyzing sources and developing conversion strategies.
Repurposing is not "rewriting the same thing." It's breaking the source into atomic units and recombining them for each platform. A 2,000-word blog post can yield 30+ independent content pieces.
| Atom Type | Definition | Extraction Example | Convertible Formats |
|---|---|---|---|
| Claim | A verifiable assertion | "Remote work increases productivity by 13%" | Tweet, card, slide |
| Data | Numbers, statistics, ratios | "2024 AI market size: $184B" |
| Infographic, chart, tweet |
| Story | Person/event-based narrative | "Company A's transformation case" | Thread, carousel, video script |
| Process | Step-by-step methodology | "5-step OKR setting method" | Guide, carousel, checklist |
| Quote | Citations, aphorisms | "'Failure is the mother of success'" | Text card, tweet, slide |
| Question | Thought-provoking questions | "What time is your team most productive?" | Poll, comment prompt, opening |
| Contrast | Comparisons | "Traditional vs. Agile methodology" | Comparison table, carousel, infographic |
| Definition | Concept definitions | "What is OKR?" | Educational content, slide, short-form |
Visually map the source's structure:
Source Content
├── Introduction
│ ├── [Claim] Core assertion
│ └── [Data] Supporting data
├── Body 1
│ ├── [Definition] Concept definition
│ ├── [Process] Methodology
│ └── [Story] Case study
├── Body 2
│ ├── [Contrast] Comparative analysis
│ ├── [Data] Statistics
│ └── [Quote] Expert citation
└── Conclusion
├── [Claim] Final assertion
└── [Question] Question for the reader
Assign a reuse value score to each atom:
| Criterion | Weight | Description |
|---|---|---|
| Independence | 30% | Does it make sense without context? |
| Emotional Response | 25% | Does it trigger surprise/empathy/outrage? |
| Shareability | 25% | Is it information worth passing along? |
| Visualizability | 20% | Can it be expressed as a graph/image? |
Set conversion priority by reuse value score:
Add elements not in the source but needed for conversion:
Recommended slides = (Presentation time in minutes × 1.5) + 3
- +3: Cover (1) + Table of Contents (1) + Q&A (1)
- ×1.5: ~40 seconds per slide
| Type | Text Amount | Visual Ratio | Use Case |
|---|---|---|---|
| Title | Title + subtitle | 100% background image | Section dividers |
| Key Message | 1 sentence | 70% | Core claim emphasis |
| Data | Labels only | 80% chart/graph | Statistics, comparisons |
| Process | Step names only | 70% flowchart | Methodology, steps |
| Comparison | 2-column table | 50% | A vs B |
| Quote | Quote + source | Speaker image | Authority/emotion |
| Story | 3–4 sentences | 50% related image | Cases, anecdotes |
| Source Type | Expected Atoms | Expected Derivative Content |
|---|---|---|
| 2,000-word blog | 15–25 | 8 tweets + 2 carousels + 15 slides + 3 short-form |
| 5,000-word report | 30–50 | 3 blogs + 5 carousels + 25 slides + 2 newsletters |
| 30-min interview | 20–30 | 5 clips + 10 tweets + 1 blog + 3 carousels |
| 60-min talk | 40–60 | 3 blogs + 5 carousels + 15 tweets + 2 newsletters |