Turn one asset into a week of content

Content lead / social media manager / solo creator / founder building in public · Assemble in ~15 min; first run in <2 min once installed.

GTMEdit flowon X◐ readiness 47

step 1connector

Ingest & transcribe the cornerstone asset

⚡ bring your own tool

step 2ready

Build reusable brand-voice profile

brand-voice11 alts

step 3ready

Atomize into platform-native posts, threads, carousels & clip scripts

content-engine7 alts

step 4ready

Author the newsletter edition from the same asset

content-repurpose7 alts

step 5ready

Build channel-by-channel distribution plan with timing/cadence

ink-distribute2 alts

step 6connector

Schedule & publish across channels

⚡ bring your own tool

step 7connector

Cut actual video/audio clips from the source

⚡ bring your own tool

Did this recipe work for you?

What you get

▸Tweet thread + LinkedIn post + newsletter blurb + clip scripts from one asset
▸All in your extracted brand voice

tools: optional scheduler (Typefully/Buffer)

tokens: ~$0.5-1 per asset

≈ near-zero

What stays yours

· Voice check before publishing
· Scheduling (until a scheduler is connected)

The problem

When I publish a cornerstone asset (blog, talk, podcast, video), I want it atomized into platform-native posts, threads, carousels, clips, and a newsletter in my brand voice and scheduled across channels, so I maximize reach per asset without hours of manual reformatting per platform.

Readiness

The creative core assembles cleanly from the library: voice (107), multi-format atomization (108), newsletter (295) and a timed distribution plan (437) are all ready and rich/solid. What you must bring is the plumbing at both ends — transcription to get the asset into text, a scheduler to actually drip-post on the planned cadence, and a video tool to cut real clips (the skills only write clip scripts). So roughly 4 of 7 steps are ready out of the box; the 3 holes are data/tool plumbing, not missing skills.

Cybernetic layers

Memorybyo

Needs to remember the brand-voice profile and which atoms were already published per asset across runs. brand-voice (107) reuses the profile only within a session; persist the VOICE PROFILE to a file (e.g. ~/.brand/voice.md) and keep a published-log so atoms aren't reposted. No candidate provides a durable store.

Background / schedulingbyo

The distribution plan from ink-distribute (437) is timed (Day0/Day1/Week3) so it benefits from unattended execution, but the artifacts only generate plan+copy. Drip-posting on the cadence requires a cron/scheduler firing into the byo publisher (Typefully/Buffer); not handled by any candidate.

Harnessready

Runs as Claude Code skills invoked in sequence (brand-voice -> content-engine -> content-repurpose -> ink-distribute). One operator command per asset; harness is fully ready, the gaps are the external transcription/scheduler/clip tools.

Click any step to see what fills it — and the ranked alternatives you can swap in.