content-pillar-atomizer
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", "platform-native content", "atomize", "content multiplication".
npx skills add Affitor/affiliate-skills --skill content-pillar-atomizer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Content Pillar Atomizer 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. ## Stage S2: Content Creation — This IS content creation, just at 10x scale. One piece of deep work becomes a month of social content. ## When to Use - User has a blog post, article, or long-form content and wants to maximize its reach - User asks to "repurpose" or "atomize" content - User says "turn this into social posts", "content multiplication", "pillar content" - After `affiliate-blog-builder` (S3) produces an article — atomize it into social - User wants to maintain consistent content output without creating from scratch daily ## Input Schema ```yaml pillar_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 prom
- Stage
- When to Use
- Input Schema
- Workflow
- Step 1: Analyze Pillar Content
- Step 1.5: Check Platform Performance for This Topic (data-driven)
- Step 2: Platform Mapping
- Step 3: Generate Micro-Content
- Step 4: Tag for Tracking
- Step 5: Self-Validation
- Output Schema
- Output Format
- Error Handling
- Examples
What does the content-pillar-atomizer skill do?
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", "platform-native content", "atomize", "content multiplication".
How do I install it?
Run `npx skills add Affitor/affiliate-skills --skill content-pillar-atomizer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Affitor/affiliate-skills, a repository with 586 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.