Playbook · Repurposing

Playbook: Repurpose each newsletter issue across platforms with agents

Four creators turn one piece of writing or one recording into posts for X, Reddit, LinkedIn, Substack Notes and shorts, and keep a person on the final yes.

Teardowns: 4Stack: Claude Code · Typefully · SlackHuman approval: before posting
Sharyph · Daria Cupareanu · Lucija Tomšić · Chris Alarcon Verified Oct 16, 2026 Markdown copy

Who it’s for: newsletter writers who publish every week and skip the social posts afterwards.

Tools these creators use: Claude Code skills and slash commands, Typefully (Sharyph); Claude Code Routines, Gmail and Slack (Daria Cupareanu); Claude, a Vercel dashboard, Supabase and a CSV bulk-scheduler on top of Substack’s scheduler (Lucija Tomšić); Claude Code and the Blotato scheduler (Chris Alarcon).

The steps

  1. Draw the line on what stays yours. Daria keeps the newsletter writing: “Distribution gets automated, but nothing publishes without me.” Lucija’s system never touches the article itself. Chris keeps recording and approving for himself. Sources: Daria (teardown, original); Lucija (teardown, original); Chris (teardown, original)

  2. Write the voice files first. Lucija’s three core files are a voice profile, an “about me” with real stories and a list of writing habits to avoid. She says they “do 80 percent of the work”, and her writer agent is “not allowed to invent my life”. Source: Lucija (teardown, original)

  3. One saved command per output. Sharyph runs /tweet (8-12 standalone tweets under 280 characters, no hashtags or emojis) and /create-thread (an X thread with a CTA back to the newsletter) on each new issue. Source: Sharyph (teardown, original)

  4. Rewrite natively per platform, don’t copy-paste. Chris’s system writes native rewrites of the week’s ideas for the newsletter and LinkedIn, “never a copy-paste”. The system drafts and he edits. Source: Chris (teardown, original)

  5. Use the article to answer communities. Daria’s agent drafts a Reddit post from each article with suggested subreddits, and scans subreddits for questions her work already answers, using her internal wiki. Source: Daria (teardown, original)

  6. Run on a schedule that doesn’t need your laptop. Daria’s Claude Code Routine wakes every six hours in Anthropic’s cloud. Lucija’s engine runs every Wednesday at 6pm and emails her when drafts are ready. Sources: Daria (teardown, original); Lucija (teardown, original)

  7. Review everything in one place before it goes out. Daria approves, rejects or rewrites each draft in Slack. Lucija edits in a dashboard and clicks “approve and push to scheduler”. Sharyph’s /push-to-typefully shows a schedule preview and waits for his confirmation. Sources: Daria, Lucija, Sharyph (teardowns: Daria, Lucija, Sharyph; originals: Daria, Lucija, Sharyph)

  8. Bulk-schedule. Lucija built a CSV bulk-scheduler first, because Substack’s scheduler takes one note at a time. Sharyph pushes drafts into Typefully. Chris batch-uploads shorts to TikTok, YouTube Shorts and Instagram through Blotato. Sources: Lucija (teardown, original); Sharyph (teardown, original); Chris (teardown, original)

  9. Feed your edits back in. Daria’s agent reads all her edits every Monday and rewrites its own instructions and skills. Lucija’s Retro Analyst treats each hand edit as a correction and writes it into a capped voice file, where her latest behavior wins. Sources: Daria (teardown, original); Lucija (teardown, original)

  10. Add one lane at a time. Chris’s minimum version: write the process as numbered steps, automate the transcript, build one rewrite lane, add one QA question per stage, and only then add platforms. Lucija: “You do not build all eight on day one.” Daria does a task by hand until she learns how Claude handles it. Sources: Chris (teardown, original); Lucija (teardown, original); Daria (teardown, original)

Postby’s suggestion: if you only build one thing this week, build step 3 for a single platform plus the confirm step from step 7.

Human approval points

  • Daria: every draft in Slack. LinkedIn posts publish only after she approves.
  • Lucija: the dashboard approval before anything reaches Substack.
  • Sharyph: one confirmation on the Typefully schedule preview.
  • Chris: he reviews the polished cuts, edits the rewrites and picks next week’s topics.

Common failure points (as the creators report them)

  • Output drifts toward generic when the week’s article is thin, and her retro agent over-rates its own work (Lucija).
  • Timing is a guess because Substack doesn’t show when readers are online (Lucija).
  • Two jobs sharing a folder spliced in the wrong captions, and broken newsletter links went unnoticed for a while (Chris).
  • Daria still does 20% of Instagram, Facebook and Threads repurposing by hand and isn’t happy with the carousel copy yet.

Caveats carried over

  • Sharyph: skill files are paywalled ($39/month); the 3-4 hours to under 30 minutes figure is his estimate. X @sharyph_ Unverified.
  • Daria: the detailed breakdown is paywalled; no traffic or subscriber figures. X @dariacupareanu is linked in her post but Unverified independently.
  • Lucija: the post body doesn’t name the author; the name comes from brisk.vision’s page metadata. No engagement results; the post is a referral push. X: Unverified.
  • Chris: runs a top-tier Claude plan plus two $100 plans; says a leaner version works on one $20 plan.

Examples

Get one teardown a week.

Same format, a new operator every issue. Double opt-in.