Marketing

My newsletter becomes Twitter threads without extra work

I write a weekly newsletter about product development. About 2,000 subscribers. The problem was that I'd spend 3 hours writing the newsletter, send it, and then have nothing to post on Twitter for the rest of the week. The ideas were all in the newsletter, but rewriting them as threads felt like doing the same work twice.

Now after I send each issue, I forward the text to my agent. It pulls out the 2-3 ideas worth threading, writes them as Twitter-native content, and gives me standalone tweets I can schedule throughout the week.

The agent

Same Content Repurposer. For newsletters specifically, it identifies which sections have the most thread potential. Not everything in a newsletter makes a good thread. The agent picks the ideas that work as self-contained stories.

Setting it up

If you have a Content Repurposer, skip ahead. Otherwise:

Find the agent

Head to the Hiregents marketplace and find Content Repurposer. Read the skill file if you want to know exactly what it can do. Everything is transparent.

Sign in

Click Deploy. You'll get a magic link to your email. No passwords, no account setup. Click the link and you're in.

Pick a plan

Hobby ($39/mo) or Pro ($49/mo). Both get you a private server. The difference is the AI model: Hobby runs Gemini Flash, Pro runs Claude Sonnet. Annual billing saves 25%.

Connect your keys

Two things needed: an OpenRouter API key (takes 30 seconds to create at openrouter.ai) and a Telegram bot token (message @BotFather on Telegram, type /newbot, follow the prompts). Both get validated in real-time before you can continue.

Review and deploy

Check the summary: agent name, plan, email. Hit Deploy. You'll go through Stripe checkout and land on a status page.

Wait about 5 minutes

The status page shows a progress circle while your server boots. Docker pulls, security gets configured, the agent installs its tools. You don't need to stay on the page. It'll be ready when you come back.

Open Telegram

Find your bot on Telegram (the one you created with BotFather). Send /start. Content Repurposer is live.

What the conversation looks like

12:34

Content Repurposer

online

Today

Here's this week's newsletter. Pull out the best thread ideas: [2,000 word newsletter about shipping culture, feature flags, and why most roadmaps are fiction]

12:34

Content Repurposer

Three strong thread angles from this issue: Thread 1: "Why your roadmap is fiction" (7 tweets) 1/ Your Q3 roadmap is a guess. Here's why that's fine. 2/ We planned 12 features for Q2. Shipped 4. The other 8? Didn't matter. Our best feature this quarter wasn't on the roadmap at all... [full thread] Thread 2: "Feature flags changed how we ship" (5 tweets) 1/ We used to deploy once a week. Now it's 4-5 times a day. The difference: feature flags. 2/ Every new feature ships behind a flag. Code goes to production on day one. Users see it when we're ready... [full thread] Standalone tweets (5): - "The best roadmap item this quarter was something a customer asked for on Tuesday and we shipped by Thursday." - "Feature flags aren't about hiding broken code. They're about separating deployment from release." - "If your planning cycle is longer than your learning cycle, you're planning too much." - "Most roadmaps are promises made to stakeholders, not predictions of what users need." - "Ship daily or ship weekly, doesn't matter. What matters is that you ship before you're comfortable." That's a week of content from one newsletter.

12:34

Message

What I got

A full week of Twitter content from one newsletter, pulled and formatted in under 3 minutes. The threads drive traffic back to the newsletter, which grows subscribers, which gives me more material to repurpose. The cycle feeds itself.

Try it yourself

Deploy Content Repurposer View agent profile