Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Take 1 blog post or article and generate 15-30 platform-native micro-content pieces. Not reformatting — re-contextualizing for each platform's culture. Triggers on: "atomize this content", "repurpose my blog post", "turn this into social posts", "content atomizer", "pillar content", "one to many content", "repurpose content", "multiply my content", "content explosion", "turn article into posts", "break down this article", "micro content from blog", "content pillar strategy", "10x my content", "p
.claude/skills/affitor-content-pillar-atomizer/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-07 | ✗→✓ | ▲ Improved | 48% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 106% | 0% |
| case-17 | ✗→✓ | ▲ Improved | 100% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 108% | 0% |
| case-21 | ✗→✓ | ▲ Improved | 166% | 0% |
Take 1 blog post or article and generate 15-30 platform-native micro-content pieces. This is NOT reformatting — it's re-contextualizing each piece for the platform's culture, format, and audience expectations. A LinkedIn post reads nothing like a Reddit comment, even if they carry the same insight.
S2: Content Creation — This IS content creation, just at 10x scale. One piece of deep work becomes a month of social content.
affiliate-blog-builder (S3) produces an article — atomize it into socialyamlpillar_content: string # REQUIRED — the full blog post/article text, or URL to fetch platforms: string[] # OPTIONAL — target platforms # Options: "twitter", "linkedin", "reddit", "tiktok", "email", "threads" # Default: ["twitter", "linkedin", "reddit"] product: object # OPTIONAL — affiliate product being promoted name: string url: string reward_value: string mode: string # OPTIONAL — "quality" | "volume" # Default: "quality" tone: string # OPTIONAL — "professional" | "casual" | "edgy" | "educational" # Default: inferred from pillar content
Chaining from S3: If affiliate-blog-builder was run, use its output article as pillar_content.
Chaining from S1 monopoly-niche-finder: Use monopoly_niche positioning to angle all micro-content.
web_fetch to retrieve contentBefore atomizing equally across all platforms, understand which platforms are hot for this topic:
If trending-content-scout ran:
pattern_analysisengagement_benchmark.platform_averages — which platform has highest engagement for this keyword?Quick check (no scout data):
web_search "[topic] youtube vs tiktok vs linkedin" → which platform dominates discussion?Apply to atomization allocation:
Platform allocation example:
Default (no data): Twitter: 5 | LinkedIn: 3 | Reddit: 3 | TikTok: 3 | Email: 2
Data-driven (TikTok hot): Twitter: 3 | LinkedIn: 1 | Reddit: 2 | TikTok: 6 | Email: 2
Data-driven (LinkedIn hot): Twitter: 3 | LinkedIn: 5 | Reddit: 2 | TikTok: 2 | Email: 2Read shared/references/platform-rules.md for platform-specific rules.
For each platform, map the culture:
| Platform | Format | Tone | Length | CTA Style | |---|---|---|---|---| | Twitter/X | Thread or single tweet | Punchy, opinionated | 280 chars or 5-10 tweet thread | Last tweet | | LinkedIn | Story or insight post | Professional, first-person | 1300 chars | Soft CTA in comments | | Reddit | Value-first post/comment | Helpful, honest, skeptical-aware | Variable | Disclosure + subtle | | TikTok | Script with hook | Casual, energetic | 30-60s script | Verbal + bio link | | Email | Newsletter section | Conversational | 200-400 words | Direct link | | Threads | Conversational take | Casual, authentic | 500 chars | Bio link |
For each platform, generate pieces from different atomic units:
Each piece must:
Tag each piece with:
yamloutput_schema_version: "1.0.0" atomized_content: pillar_title: string total_pieces: number platforms_covered: string[] pieces: - platform: string type: string # "thread" | "single" | "story" | "script" | "email" | "comment" content: string # The actual content, ready to post insight_source: string # Which atomic unit from the pillar has_affiliate_link: boolean suggested_timing: string # e.g., "Tuesday 9am" variant_id: string # For volume mode A/B tracking content_pillars: string[] # Atomic units extracted (for chaining) chain_metadata: skill_slug: "content-pillar-atomizer" stage: "content" timestamp: string suggested_next: - "social-media-scheduler" - "email-drip-sequence" - "ab-test-generator"
## Content Atomizer: [Pillar Title]
### Pillar Analysis
- **Atomic units extracted:** X insights
- **Platforms:** [list]
- **Total pieces generated:** XX
---
### Twitter/X (X pieces)
**Thread: [Title]**
🧵 1/ [first tweet]
2/ [second tweet]
...
[last tweet with CTA]
**Standalone Tweet:**
[tweet text]
---
### LinkedIn (X pieces)
**Story Post:**
[full LinkedIn post]
---
### Reddit (X pieces)
**Post: r/[subreddit]**
Title: [title]
[body with disclosure]
---
[Continue for each platform]
### Posting Schedule
| Day | Platform | Piece | Time |
|---|---|---|---|
| Mon | Twitter | Thread | 9am |
| Tue | LinkedIn | Story | 8am |
| Wed | Reddit | Post | 12pm |affiliate-blog-builder."Example 1: "Atomize my HeyGen review blog post into social content" → Extract 6 key insights, generate 15 pieces across Twitter (thread + 3 tweets), LinkedIn (2 posts), Reddit (2 posts), TikTok (2 scripts).
Example 2: "Turn this article into LinkedIn and Twitter content" → Focus on 2 platforms only. Generate 3 LinkedIn posts (story, insight, question) and 5 Twitter pieces (thread, 3 tweets, hot take).
Example 3: "Atomize in volume mode" (after affiliate-blog-builder) → Pick up article from chain. Generate 25-30 pieces with multiple variations per platform for A/B testing.
After 7 days, check: which platform generated the most affiliate link clicks? Double down on that platform, reduce effort on underperformers.
> Next step — copy-paste this prompt: > "Schedule all my atomized content for the next 30 days" → runs social-media-scheduler
social-media-scheduler (S5) — atomized pieces ready to scheduleemail-drip-sequence (S5) — email-format pieces for sequencesab-test-generator (S6) — volume mode variants for testingtrending-content-scout (S1) — platform performance data for allocationcontent-angle-ranker (S1) — recommended angle for the pillar topicaffiliate-blog-builder (S3) — pillar content to atomizemonopoly-niche-finder (S1) — positioning angle for all piecescontent-repurposer (S7) — repurposed content to atomize furtherperformance-report (S6) reveals which platforms and content types perform best → focus future atomization on winning platformsBefore delivering output, verify:
Any NO → rewrite before delivering.
When mode: "volume":
yamlvolume_output: variants: - id: string # e.g., "tw-v1", "tw-v2" content: string # The variation angle: string # What makes this one different
shared/references/platform-rules.md — Platform-specific culture, format, and CTA rulesshared/references/ftc-compliance.md — FTC disclosure per platform typeshared/references/affitor-branding.md — Branding rulesshared/references/flywheel-connections.md — Master connection mapOther measured skills in the registry, with their headline benchmark lift.