content-atomizer
Turns one piece of finished content (blog post, newsletter, podcast, video) into platform-native social assets for the 2-3 platforms the brand actually operates, with depth on a few platforms instead of rephrased spray across eight. Use when source content exists and needs distribution, when a post's comments need ranked reply drafts, or when a week of posts should be planned from one source.
How do I install this agent skill?
npx skills add https://github.com/boringmarketer/boring-marketing-skills --skill content-atomizerIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is designed to repurpose content into platform-native social media assets. It interacts with external URLs and integrates with social media scheduling APIs to automate posting. The primary security consideration is the potential for indirect prompt injection when processing untrusted content from the web or user-pasted comments.
- Socketpass
No alerts
- Snykfail
Risk: CRITICAL · 2 issues
What does this agent skill do?
Content Atomizer
Turn one finished piece into the few platform-native assets it actually deserves, and nothing else. The judgment this skill carries: platform selection and native depth are the work; volume is the failure mode. Rephrased-spray content is a strategy for being ignored at scale; platform-specific evidence lives in references/platform-facts.md. This skill is a floor, not a ceiling. If the content in front of you deserves a better path than the one below, take it and say why in one line.
Context
Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run:
python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for content-atomizer
(If the script or python3 is unavailable, read the files named in reads: directly, section-anchored where specified. If none exist, proceed standalone and ask only for what the task strictly requires.)
What each input does here:
- voice-profile#platform-adaptations: the per-platform voice table. It is the ONLY source of voice adjustment in this skill; never invent a parallel adaptation table. No profile means ask one question ("how formal, and any words you'd never use?") and write in a clean neutral register.
- learnings: platform performance priors. Apply them. Mention one only when it changed the work, as a single line in the note ("Your carousels outperformed text posts 3/3 in May, so LinkedIn gets one").
- algo-cache: per-brand dated platform facts, if /performance-review or a prior refresh has written any. Where it conflicts with this skill's reference file, the fresher
last-verifiedwins.
Freshness gate (run before generating): load references/platform-facts.md. If today is past last-verified + ttl-days, refresh per the instruction in its header, update the file, and say so in one line in the note. Never generate against stale algorithm facts silently.
Modes
| Mode | Trigger | Output |
|---|---|---|
| Atomize (default) | Source content + "repurpose / atomize / post from this" | 3-6 native pieces across 2-3 platforms |
| Engagement replies | "draft replies," pasted comments, a post URL + "respond" | Ranked reply drafts + relationship flags |
| Calendar | "content calendar," "week of posts from this" | Atomize output + dated schedule.md |
| Full fan-out | Explicit only: "all platforms," "everything," "max distribution" | Wide coverage, after a one-line warning |
Quick Mode applies: "give me an X post from this" means one X post, fast. Skip platform selection, skip the brief, deliver and lint it.
Phase 1: Platform judgment (this is the skill)
Before writing anything, decide where this content should go and how deep. Two questions, in order.
1a. Which platforms does this brand operate?
Evidence, in priority order: filled rows in the voice-profile platform-adaptations table (an empty or templated row means they don't really post there), platform entries in learnings, platforms named in the request. If still unclear, ask ONE question: "Which 2-3 platforms do you actually post on?" Do not default to all eight. A platform the user doesn't operate gets nothing, because orphan posts on a dead account are worse than absence.
1b. What does THIS content deserve on each operated platform?
Per platform, assign one of four treatments:
- Native deep: the content's strongest material, rebuilt in the platform's native format from scratch. The piece should read like it was conceived for the platform.
- Native light: one standalone post carrying a single extractable insight.
- Link-in-reply: a self-contained post that delivers the core value, with the source link in the first reply (on X, links in the post body cost 30-50% of reach; see platform-facts). The post must work for someone who never clicks.
- Skip, and say why. "This has nothing for TikTok" is a correct, complete answer. Skipping is not under-delivery; spraying is.
Fit judgment by content shape:
| Source material | Strong fit | Weak fit |
|---|---|---|
| Framework / numbered process | LinkedIn carousel or document, X thread | Short video (compresses badly) |
| First-person story with a turn | X long-form post, LinkedIn text, TikTok/Reel script | Carousel (kills the pacing) |
| Original data / research | X post + chart, LinkedIn text, Reddit deep post | Instagram (unless /creative builds the visual) |
| Contrarian argument | X standalone post, Threads | LinkedIn (argue with evidence there, not edge) |
| Tutorial / how-to | TikTok/Shorts script, carousel | Threads, Bluesky |
| Opinion / commentary | Threads, X, Bluesky | YouTube |
Default budget: 2-3 platforms, 1-2 pieces each (3-6 total). Depth beats coverage. Every piece justifies itself by treatment, not quota; exceed the budget when the source and the brand's footprint genuinely earn it, stating why. Full fan-out only on explicit request, prefaced once with: "Heads up: broad fan-out of one source underperforms native depth on the platforms you actually run, and current rankers demote rephrased cross-posts. Doing it as asked."
State the plan in 3-5 lines (platform, treatment, why, plus skips with reasons) before generating. If the user redirects, that's the cheapest possible edit.
Worked example (illustrative; source: Hartline Plumbing's 2,400-word guide to water heater replacement costs in Dallas, a sample business; the brand operates LinkedIn + X and has a dormant Instagram):
Plan: "What a water heater swap actually cost our Dallas customers in 2026"
LinkedIn native deep the cost-by-tank-size breakdown is carousel-shaped; your
carousels beat text 3/3 in May
X native light + link-in-reply the headline number stands alone; the
job-by-job detail stays in the guide, linked in reply 1
Instagram skip account dormant since March; cost charts need /creative
visuals to be worth posting there at all
3 pieces total. Say the word if you want wider coverage.
Phase 2: Extract
Mine the source once, before writing anything. Pull only elements that survive standalone. If a point needs the surrounding article to make sense, it isn't an atom, it's a fragment.
- Core insight: the one sentence someone should repeat to a colleague
- Supporting points: 3-7, each carrying its own evidence
- Stories: concrete scenes with a turn, not "we learned a lot"
- Data points: specific numbers with their context attached
- Contrarian takes: positions a smart peer could actually dispute
- Quotable lines: sentences that earn a screenshot
If the source is a URL, fetch it (Firecrawl if FIRECRAWL_API_KEY is set, else WebFetch). For audio/video, work from the transcript and note timestamps next to extracted moments, because they become clip references.
Write the extraction to brief.md (skip in Quick Mode). Honest sparseness beats padding: a thin source yields 2 atoms, and the brief should say so rather than inflate filler into "insights."
Phase 3: Transform (native craft per platform)
Three inputs govern every piece: the extraction (what to say), the platform's native format (how it's shaped), and the brand's platform-adaptations row (how it sounds). Algorithm specifics (weights, penalties, format rankings, length limits) live in references/platform-facts.md; consult it per platform while drafting. What follows is the evergreen craft.
Load references/slop-patterns.md before writing any hook or CTA. It is the lint list: hooks and structures that pattern-match as AI or engagement bait and are demoted by rankers and readers alike. Hook craft is built from first principles there: specificity over formula, earned tension, credential-in-context, the first line surviving standalone.
What "native" means per platform
Templates: when the user wants copy-paste scaffolds or a specific format, load references/platform-templates.md and fill the matching template; otherwise write natively.
X. The atom is the standalone post; it must be the value, never the ad for the value. Threads only when the material genuinely sequences, and each post still has to survive alone in a quote or screenshot. Essay-shaped material becomes one long-form post, not a 12-part thread. Links default to a first reply, since a body link spends 30-50% of reach (platform-facts) and so needs a reason worth that. Constructive framing over combat: the current ranker rewards the former and suppresses the latter, and so do the readers worth having.
LinkedIn. Lead with the insight, not the persona. The first 2-3 lines render above the fold, which makes them the entire hook surface, and they must contain a specific claim, not throat-clearing. One idea per post, argued with evidence. Frameworks and enumerable material become carousels/documents (route slide design to /creative); narrative insight becomes a text post. If the brand runs a LinkedIn newsletter, flag long material for it, since newsletters bypass the feed entirely.
Instagram. Visual-first: the asset carries discovery, the caption carries voice. Carousels for frameworks, Reel scripts for spoken material. The caption's first line is its hook (it truncates in feed). Always route visual production to /creative with the slide-by-slide text. Skip Instagram entirely rather than ship a text-on-gradient afterthought.
TikTok / YouTube Shorts. Spoken scripts, written for the ear: contractions, fragments, no preamble. The hook is visual AND verbal in the first second, so start mid-action or mid-claim. Script format: [0-2s hook] [body beats with timestamps] [close]. One idea per video; a 5-point listicle is five videos or one carousel elsewhere. End where rewatching makes sense rather than with a begging CTA.
Threads. The take, not the lecture. Conversational register, the voice off-duty. Single posts or 3-4 post mini-threads that invite replies by leaving genuine room for disagreement, not by asking "thoughts?"
Reddit. The brand voice nearly disappears: community-first, plain first-person, zero marketing scent, affiliations disclosed. Long-form value posts that would be worth reading if the author had nothing to sell. Match the target subreddit's norms (read its rules before drafting) and never link to owned content unless asked in comments. Only generate Reddit content when the user names a community they genuinely participate in.
Bluesky. Substantive short text for a plateaued but engaged niche. Only when the user operates there; never as default coverage. Voice: apply the X row from voice-profile#platform-adaptations. Bluesky is text-first like X, minus the link penalty (links in the post body are fine there).
YouTube long-form and email are not atomization targets. Route to /creative (video) and /newsletter (email) instead of producing outline-shaped filler here.
Voice
Apply the platform's row from voice-profile#platform-adaptations to every piece: tone shift, structure and length notes, register. The test: same person, different room. If a piece would read identically on LinkedIn and X, at least one of them is not native.
Phase 4: Quality gate
Score every piece 1-10 on five dimensions before presenting, silently:
- Native fit: conceived-for-this-platform, or detectably repurposed?
- Hook: does the first line survive standalone, with a specific claim? (slop-patterns.md defines the bar)
- Specificity: does every claim trace to the source material? No invented numbers, no inflated certainty, no generic filler the source doesn't support.
- Voice match: would it pass the brand's own drift check against the adaptations row?
- Slop lint: binary. Zero matches against slop-patterns.md (hooks, CTAs, structures) and no cluster of prose tells per brand-voice's ai-tells list.
The default ship bar: ≥8 average, no dimension below 7, slop lint clean. Judgment can override in either direction with a stated reason. Below bar: rewrite the weak dimensions only, rescore, up to ~3 iterations, then present the best version. The client sees the finished pieces, never the scores or their history (keep them in notes.md). If a weakness could not be fixed, say what it is in one line in the note.
Mode: Engagement replies
Treat engagement replies as a high-leverage content surface. On X, use the current
author-engaged-reply weighting in references/platform-facts.md when triaging; reply
quality is part of how strangers decide whether an account is worth following. Treat this
mode as seriously as post generation.
Input: pasted comments/replies, or a post URL. Fetching X content usually requires auth, so attempt it (Firecrawl/WebFetch), and if it fails, say so and ask for a paste rather than guessing at thread contents. A treg token (TREG_TOKEN) is the one-key alternative for pulling post and comment data. It is one token for many data APIs, pay per call. Check its catalog for the platform first.
Triage: rank before drafting (a default order; the comments in front of you outrank the taxonomy):
- Substantive questions: answer with new information, not a restatement of the post
- Informed disagreement: the gold tier. Engage the strongest version of their point, concede what's true, add evidence. Constructive sentiment is algorithmically boosted on X and combative is suppressed, and a graceful public disagreement is the single best advertisement for the account
- Experience-sharing: commenters adding their own data or story. Amplify and build on it
- Notable/peer accounts: even thin comments from relevant peers deserve a real reply
- Generic praise: batch a short varied acknowledgment or skip; don't paste the same "Thanks! 🙏" down the column
- Bait and trolls: skip. Recommend no reply, and say why. Feeding combative threads hurts both reach and reputation
Each draft: in the platform's voice row, adds something the original post didn't say, not defensive, not sycophantic. 1-3 sentences unless the question genuinely warrants more.
Relationship flags: mark commenters worth more than a reply (repeat engagers, ICP matches, peers worth following or DMing) with a one-line reason each. This list is frequently more valuable than the replies.
Output: ./campaigns/<slug>/social/<platform>/replies-{YYYY-MM-DD}.md with ranked comments, a draft per comment, a skip list with reasons, and relationship flags.
Mode: Calendar (slimmed)
Atomize first (Phases 1-4 unchanged; the calendar never overrides the platform budget, it sequences what survived the judgment layer). Then assign dates and times:
- Spread pieces so each gets clear air: same-platform pieces at least a day apart, with the strongest piece on the brand's strongest platform first.
- Posting times: learnings priors first, platform-facts defaults second.
- 1-2 weeks from one source is the useful range. More weeks usually means more source content is needed, so say so and route to /seo-content or /newsletter.
- Reserve explicit slots for engagement: 20-30 minutes after each post for replies (see Engagement replies mode). That time is part of the post's performance, not optional aftercare.
Write schedule.md to the campaign root: frontmatter (source, date range, platforms, total posts), then a day-by-day list with time, platform, file and a one-line description.
Scheduling & posting
We use Zernio for this. It is one API and MCP that posts and schedules across about 18 platforms, priced by plan. Buffer is the free option for a few channels (its free plan covers 3 channels and includes an API key). Without either, the per-platform files and recommended_post_time do the job.
Detection: check .env for ZERNIO_API_KEY (Zernio), BUFFER_ACCESS_TOKEN (Buffer) or HOOTSUITE_API_KEY (Hootsuite). If found, offer (never assume) to queue the compatible pieces, and report which platforms the tool can't reach.
Native APIs: X API v2 posting, LinkedIn's Posts API, and the Threads API (public since mid-2024) allow direct programmatic posting. Current endpoints, tiers, and caveats are in references/platform-facts.md. Offer only when the user has credentials configured.
The gate, no exceptions: never post or schedule anything live without showing the exact final text, platform, and time, and getting explicit confirmation for that batch. In non-interactive or routine runs (workflows, scheduled sessions), write files only and queue nothing. Drafts on disk are recoverable; a bad live post is not.
Without any scheduler: include recommended_post_time in each file's frontmatter and move on. Do not lecture about connecting tools.
Output
All files are written before the chat summary, following the four-section output contract in ${CLAUDE_SKILL_DIR}/../start-here/references/output-format.md.
./campaigns/<source-slug>/
brief.md # extraction summary + platform plan w/ skip reasons
notes.md # working file: quality-check scores, priors applied, source quotes
social/
<platform>/ # only platforms that survived Phase 1
<format>-<nn>.md # e.g. text-post-01.md, thread-01.md, reel-script-01.md
replies-<date>.md # engagement mode
schedule.md # calendar mode only
Slug: kebab-case from the source title, ≤40 chars. Each content file carries frontmatter:
---
platform: x
format: long-form-post
source: "<source title>"
created: {YYYY-MM-DD}
status: draft
recommended_post_time: "<day/time or 'scheduled via Buffer'>"
---
Then the four-section chat output: ## SOCIAL POSTS: {source title} plus one line of date and what the work is for, the finished pieces first, one line per skipped platform with its reason (the full plan lives in brief.md, so do not restate it), one short Sources and assumptions note (10 lines max: what the posts were built from, any claim to confirm with the source owner, what is missing), Files saved with exact paths, What's next. Append one line per asset to ./brand/assets.md.
What's next (pick 2-4 by context):
/creative: carousel slides, charts, or video for the visual-first pieces (~15 min)/social-content: build a per-platform pattern library from what performs, beyond one-source atomization (~20 min)/newsletter: the source insights as an edition for the owned channel (~15 min)/performance-review: after a week live, feed the numbers back so the next atomization inherits real priors (~10 min)
When the user edits your work
Apply the edit, then make it stick: save a gold case to ./brand/gold/<this skill>/ and
one to three yes/no checks to ./brand/checks.md, and confirm in one line. Before handing
over any work, answer the checks the context block loaded, silently, and fix every no.
How: ${CLAUDE_SKILL_DIR}/../start-here/references/taste-loop.md.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/boringmarketer/boring-marketing-skills/content-atomizer">View content-atomizer on skillZs</a>