Creator · Affitor
Last updated · Sep 3, 2026
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 conten
Sandbox only
Install targets
Codex install prompt
Install the "content-pillar-atomizer" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/content/content-pillar-atomizer. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: 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". After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"affitor-content-pillar-atomizer","task":"Install content-pillar-atomizer","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Code review, repo analysis, testing, CI, GitHub, DevOps, and developer workflow skills.
Scenario
Coding agents
I need a coding agent that can understand a repository, edit code, and review pull requests.
Agent fit
Claude Code + OpenAI Agents + Cursor
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add Affitor/affiliate-skills --skill content-pillar-atomizer
Maintenance
active
3mo since push
Risk
Needs review
Permission surface may require sandboxing
GitHub quality
639
73/100 Quality · 78/100 Trust
Coverage tags
Review notes
Permission surface may require sandboxing · Financial research output is not financial advice; require human review before any live investment decision
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
639 GitHub stars
Repo activity
639 stars, 199 forks
Maintenance
3mo since push
License
MIT
Install
npx skills add Affitor/affiliate-skills --skill content-pillar-atomizer
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add Affitor/affiliate-skills --skill content-pillar-atomizerDo not use when
Alternative
16.3K Stars
npx skills add hardikpandya/stop-slop --skill stop-slop
Alternative
4.8K Stars
npx skills add cursor/plugins --skill unslop
Alternative
37.4K Stars
npx skills add blader/humanizer --skill humanizer
Alternative
5.8K Stars
npx skills add petergyang/no-ai-slop --skill no-ai-slop
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may inspect schemas, query databases, or work with persistent stores.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20content-pillar-atomizer%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20content-pillar-atomizer%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/affitor-content-pillar-atomizer/install
Agent should check
Copy prompt
Task: Use content-pillar-atomizer in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20content-pillar-atomizer%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/affitor-content-pillar-atomizer/install
Install command: npx skills add Affitor/affiliate-skills --skill content-pillar-atomizer
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/affitor-content-pillar-atomizer/install
LLM text format
/api/skills/affitor-content-pillar-atomizer/install?format=text
Find alternatives
/api/skills/search?q=content-pillar-atomizer&limit=3
Agent prompt
Use content-pillar-atomizer for this task. Review https://www.openagentskill.com/api/skills/affitor-content-pillar-atomizer/install, then install with: npx skills add Affitor/affiliate-skills --skill content-pillar-atomizerRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/affitor-content-pillar-atomizer
LLM text
/api/registry/manifest/affitor-content-pillar-atomizer?format=text
Install alias
/api/registry/install/affitor-content-pillar-atomizer
Recommend
/api/registry/recommend?task=Use%20content-pillar-atomizer%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code, OpenAI Agents, Cursor
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
Research agents
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO639 GitHub stars
Stars/forks activity
INFO639 stars, 199 forks; issue activity unavailable in current metadata
Recent maintenance
PASS3mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Publish consistently
I need my agent to turn research and product updates into useful content drafts.
Automate repeated work
I need my agent to automate a repeated workflow across tools and files.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Alternative shortlist
Similar skills that may fit this task.
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
--- name: content-pillar-atomizer description: > 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". license: MIT version: "1.0.0" tags: ["affiliate-marketing", "content-creation", "social-media", "copywriting", "content-strategy", "repurposing"] compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent" metadata: author: affitor version: "1.0" stage: S2-Content ---
# 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 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.
## Workflow
### Step 1: Analyze Pillar Content
1. If URL provided, use `web_fetch` to retrieve content 2. Extract: key insights (5-8), data points, quotes, frameworks, stories, opinions 3. Identify the "atomic units" — self-contained ideas that work independently 4. Note the product/affiliate angle (if present)
### Step 1.5: Check Platform Performance for This Topic (data-driven)
Before atomizing equally across all platforms, understand which platforms are hot for this topic:
**If `trending-content-scout` ran:** - Use platform-level engagement data from `pattern_analysis` - Check `engagement_benchmark.platform_averages` — which platform has highest engagement for this keyword? - Prioritize platforms where this topic has highest engagement - Adjust platform allocation accordingly (see below)
**Quick check (no scout data):** - `web_search "[topic] youtube vs tiktok vs linkedin"` → which platform dominates discussion? - Check: is this topic more visual (→ TikTok/YouTube heavy) or professional (→ LinkedIn heavy)? - Look for: which platform shows up most in search results for this topic?
**Apply to atomization allocation:** - Default: equal split across platforms - Data-driven: proportional to engagement potential - If TikTok engagement is 5x LinkedIn for this topic → generate 5 TikTok scripts, 1 LinkedIn post - If Reddit has high engagement → don't skip Reddit (often ignored by affiliates = opportunity) - If YouTube dominates → consider atomizing into YouTube Shorts scripts instead of just TikTok
**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: 2 ```
### Step 2: Platform Mapping
Read `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 |
### Step 3: Generate Micro-Content
For each platform, generate pieces from different atomic units:
- **Twitter**: 3-5 pieces (1 thread, 2-3 standalone tweets, 1 hot take) - **LinkedIn**: 2-3 pieces (1 story post, 1 insight post, 1 question post) - **Reddit**: 2-3 pieces (1 detailed post, 1-2 comment-ready responses) - **TikTok**: 2-3 scripts (1 educational, 1 hot take, 1 tutorial) - **Email**: 1-2 pieces (newsletter section, dedicated email) - **Threads**: 2-3 pieces (conversational takes)
Each piece must: - Stand alone (makes sense without reading the pillar) - Feel native to the platform (not a copy-paste resize) - Carry one clear insight or value point - Include appropriate FTC disclosure for affiliate content
### Step 4: Tag for Tracking
Tag each piece with: - Source pillar reference - Platform - Content type (thread, single, story, script) - Affiliate product (if applicable) - Suggested posting time/day
### Step 5: Self-Validation
- [ ] Each piece feels native to its platform (not copy-pasted) - [ ] Each piece stands alone without needing the pillar - [ ] FTC disclosure included where affiliate links present - [ ] No two pieces on the same platform say the same thing - [ ] Platform rules followed (Reddit skepticism, LinkedIn professionalism, etc.)
## Output Schema
```yaml output_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" ```
## Output Format
``` ## 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 | ```
## Error Handling
- **No pillar content provided**: "Paste your blog post or article, or give me the URL and I'll fetch it." - **Content too short**: "This is quite short for atomization. I'll extract what I can, but consider writing a longer pillar first with `affiliate-blog-builder`." - **No affiliate angle**: Generate content without affiliate links. Pure value content builds audience for future promotions. - **Platform not supported**: "I don't have specific rules for [platform]. I'll format it generically — review before posting."
## Examples
**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.
## Revenue & Action Plan
### Expected Outcomes - **Revenue potential**: Each atomized piece is a new touchpoint driving affiliate clicks. 15-30 pieces from 1 article = 15-30x more chances for commission - **Benchmark**: Top affiliate content creators report 2-5% of social impressions convert to link clicks. At $50 avg commission, 10,000 impressions across all pieces = $100-250/month from ONE pillar article - **Key metric to track**: Bio link / affiliate link CTR per platform — which platform drives the most clicks per impression?
### Do This Right Now (15 min) 1. Pick the **single strongest piece** from the output — the one with the most specific, surprising insight 2. Post it on your highest-engagement platform immediately 3. Add your affiliate link in bio or first comment 4. Set a reminder to post the next piece tomorrow
### Track Your Results 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`
## Flywheel Connections
### Feeds Into - `social-media-scheduler` (S5) — atomized pieces ready to schedule - `email-drip-sequence` (S5) — email-format pieces for sequences - `ab-test-generator` (S6) — volume mode variants for testing
### Fed By - `trending-content-scout` (S1) — platform performance data for allocation - `content-angle-ranker` (S1) — recommended angle for the pillar topic - `affiliate-blog-builder` (S3) — pillar content to atomize - `monopoly-niche-finder` (S1) — positioning angle for all pieces - `content-repurposer` (S7) — repurposed content to atomize further
### Feedback Loop - `performance-report` (S6) reveals which platforms and content types perform best → focus future atomization on winning platforms
## Quality Gate
Before delivering output, verify:
1. Would I share this on MY personal social? 2. Contains specific, surprising detail? (not generic) 3. Respects reader's intelligence? 4. Remarkable enough to share? (Purple Cow test) 5. Irresistible offer framing? (if S4 offer skills ran)
Any NO → rewrite before delivering.
## Volume Mode
When `mode: "volume"`: - Generate 5-10 variations per platform instead of 2-3 - Prioritize speed + variety over perfection - Tag each with variant ID for A/B tracking - Let data pick the winner (GaryVee philosophy)
```yaml volume_output: variants: - id: string # e.g., "tw-v1", "tw-v2" content: string # The variation angle: string # What makes this one different ```
## Refer
Source provenance
Decision snapshot
639 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for content-pillar-atomizer, ready for a manual X post.
A practical pick for market research: content-pillar-atomizer: Take 1 blog post or article and generate 15-30 platform-native micro-content pieces. Not reformatting — re-contextualizing... 639 stars https://www.openagentskill.com/skills/affitor-content-pillar-atomizer?ref=x
Listing + install path for content-pillar-atomizer: https://www.openagentskill.com/skills/affitor-content-pillar-atomizer?ref=x Install: npx skills add Affitor/affiliate-skills --skill content-pillar-atomizer
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to Affitor but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/affitor-content-pillar-atomizer?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/affitor-content-pillar-atomizer?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/affitor-content-pillar-atomizer/audit)
[](https://www.openagentskill.com/skills/affitor-content-pillar-atomizer?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)Affitor
@affitor
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
stop-slop
Eliminates predictable AI writing patterns from prose while preserving specific meaning and reader trust.
16.3K Starsunslop
Applies Cursor's prose-discipline rules to remove filler and AI writing tells from agent-facing and user-facing text.
4.8K StarsHumanizer
Rewrites AI-sounding text so it reads naturally while preserving every factual claim and matching the writer's voice.
37.4K Starsno-ai-slop
Audits or minimally edits drafts to remove named AI-writing patterns without flattening the author's voice.
5.8K StarsPermission surface
shell or command execution, network or browser access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness