📝 Intermediate · 20 min

Content Machine Playbook

How to produce a full week of content — blog posts, Twitter threads, LinkedIn posts, email — in a single overnight session using ZELDA and the SSBAA content pipeline. Templates included.

Updated March 23, 2026 ⏱ 20 min read 🟡 Intermediate Requires: Agent Team Blueprint
📋
RAY
Weekly brief
Sunday 20:00
🔍
ZELDA
Research cycle
Sun 22:30
✍️
ZELDA
Draft all content
Sun 23:00–02:00
🎯
YOSHI
Review + approve
Mon 06:00
📤
RAY
Publish
Mon 08:00
One brief on Sunday evening → full week of content ready Monday morning

What this guide covers

ZELDA produced four complete content files in a single overnight session on Day 1 — blog posts, a LinkedIn article, Twitter threads, and a content calendar. This guide documents exactly how we structured that workflow so you can replicate it.

The core idea is simple: content creation at volume requires a clear brief, a structured pipeline, and a review loop. Without the brief, the agent produces generic content. Without the pipeline, outputs pile up without a publishing schedule. Without the review loop, you're publishing unreviewed AI output, which is how you end up with a hallucinated agent as a blog author.

What ZELDA produced on Day 1: 3 blog posts (650–750 words each), 1 LinkedIn article (3,000 words), 4 Twitter threads (6–8 tweets each), 1 weekly content calendar, 2 LinkedIn header image briefs. Total time: one overnight session, 22:30–04:00. Human review time: 45 minutes.

The content pipeline

The pipeline has five stages. Each stage has a defined input, a defined output, and a defined owner. Nothing moves to the next stage without the previous one being complete.

  1. Brief (RAY, Sunday evening) — a structured document covering the week's themes, key messages, target audience, any specific angles or stories to use, and what not to say.
  2. Research (ZELDA, 22:30) — ZELDA reads the brief, scans competitors, identifies current conversation in the space, pulls relevant data points, and writes a research summary before touching any content.
  3. Draft (ZELDA, 23:00 onwards) — all content drafted from the research summary. Blog post first, then adapt down to LinkedIn, then Twitter threads, then email. Same core ideas, different formats.
  4. Review (YOSHI, 06:00) — YOSHI checks all outputs against the brief: on-message, correct author attribution, no fabricated claims, no hallucinated agents. Flags anything that needs RAY's attention.
  5. Publish (RAY, 08:00) — RAY reviews YOSHI's flagged items, approves the rest, and publishes to the relevant platforms.

Writing the brief

The quality of ZELDA's output is directly proportional to the quality of your brief. A vague brief produces generic content. A specific brief produces content that sounds like you wrote it.

📋 Weekly Content Brief Template
Week theme
Why AI agents fail silently and what to do about it
Core message (one sentence)
Silent failure is more dangerous than loud failure because you don't know it's happening
Specific stories/examples to use
FOX going dark for 6 hours on Day 2. YOSHI's ping protocol catching it. The false agent hallucination.
Target reader
Non-technical small business owner who's heard about AI agents but hasn't tried them yet
Tone
Honest, direct, first person. No hype. Show problems as well as wins.
Do not mention
Specific API key values, employer, personal location, revenue figures we haven't confirmed
CTA for all pieces
ssb-aa.com — $10 founding spot, 97 remaining

Content calendar automation

ZELDA produces a weekly content calendar every Monday at 09:00 as a cron job. The calendar maps each piece of content to a day and platform, ensures variety across the week, and prevents the same topic appearing on the same platform twice in a row.

Mon
Tue
Wed
Thu
Fri
Sat
Sun
Mon
Blog post
Tue
LinkedIn post
Wed
Thu
LinkedIn post
Fri
Blog post
Sat
Sun
Brief day
# The Monday content cron job
openclaw cron add "Weekly content calendar" "0 9 * * MON" \
"Read /workspace/content-brief.md and produce this week's content calendar.
Output to /workspace/delivery-queue/content-calendar-YYYY-MM-DD.md.
Include: 2 blog post titles, 4 Twitter thread hooks,
2 LinkedIn post angles, 1 email subject line.
Assign each to a day. No duplicate topics on same platform."

Platform formats

The same core idea adapts to each platform. ZELDA knows the format rules for each — you just need to tell her which platforms you're targeting in the brief.

📝
Blog
650–800 words · first person · one idea per post
Hook in first sentence. No intro paragraph. Subheadings every 200 words. End with one clear CTA. Author: RAY.
🐦
Twitter / X
6–8 tweets · hook tweet under 200 chars
Hook tweet must standalone. Each tweet max 280 chars. End with CTA tweet linking to blog or ssb-aa.com. Thread number in each tweet.
💼
LinkedIn
1,500–2,500 chars · personal · data-led
First line is the hook (no "I" at start). Short paragraphs, 1–2 sentences. One stat or specific number per post. 3–5 hashtags at end.

Brand voice consistency

The biggest risk with AI-generated content is generic output that sounds like every other AI-generated content. ZELDA avoids this when the brief is specific, but the brand voice rules also need to be written into her system prompt.

Here are the exact rules we use in ZELDA's SOUL.md file:

# ZELDA brand voice rules — excerpt from SOUL.md
ALWAYS:
- Write in RAY's voice: direct, honest, no corporate speak
- Use specific numbers, timestamps, and real examples
- Show problems alongside wins — we build in public
- One idea per piece. Never try to cover everything.
NEVER:
- "Revolutionary", "cutting-edge", "game-changing"
- Passive voice for key claims
- Invented statistics or unverified claims
- Mention RAY's employer, location, or salary
- Credit content to any agent other than RAY
- False agent entries. These do not exist.

The review loop

YOSHI reviews all ZELDA outputs before anything is marked ready to publish. The review checklist:

YOSHI flags anything that fails a check and includes it in the morning brief with a specific note. RAY reviews flagged items before publishing. Everything that passes goes into the approved queue.

Scheduling and publishing

We use Typefully for Twitter scheduling — ZELDA writes the threads, RAY pastes them into Typefully and schedules. LinkedIn posts go directly. Blog posts deploy via the Next.js content pipeline when FOX merges the MDX files.

💡 Coming soon: Direct Typefully API integration so ZELDA can schedule Twitter threads automatically without RAY's manual paste step. This is on the roadmap for the founding member community to vote on.

What to measure

Content without measurement is guessing. The three metrics we track weekly:

ZELDA produces a one-page performance summary every Monday alongside the new content calendar. It covers last week's top performer, lowest performer, and one recommendation for this week.