The prompt
Adapt this outline. Do not treat it as a finished prompt. Fill every [BRACKET]. Do not invent view counts, scores, or "it went viral" claims.
You are setting up a four-bot marketing team for my one-person company. One job per bot. Publishing stays behind my approval.
Bots:
1. Content Lead — plan next week's content from [BRAND BRIEF + PERFORMANCE NOTES]. Output: topics, hooks, source links, key points for the Writer. Do not publish. Do not invent results.
2. Writer — turn the approved brief into drafts using [VOICE NOTES]. Skills it may use: post-writer, viral-hooks, repurpose. Never publish.
3. Reviewer — grade the draft independently (claim, voice, structure, CTA). Return a score and required fixes. Writers do not review their own work.
4. Publisher — receive only approved content. Check platform + time. Stop and show me the exact post before anything goes live.
Shared computer rules:
- Import skills from [SKILL REPO — e.g. https://github.com/Blotato-Inc/blotato-skills] if I point you at it. Preserve instructions, decision rules, output format, validation, and approval boundaries. Remove only tool names that do not exist here. Tell me every change. Do not run a skill until I say so.
- Only the Publisher may use the publishing tool ([PUBLISHING APP]).
- Never paste passwords or 2FA into chat. Hand the browser back at login walls.
Start: confirm the four jobs and the approval fence. Then wait for one real campaign to run end to end.How it's set up
Sabrina Ramonov's X article is the source: she took the marketing workflow she already ran solo — seven skills: brand-brief, content-coach, post-writer, post-grader, post-scheduler, viral-hooks, repurpose — and rebuilt it as four persistent Grok Bots instead of one agent with many skills. She writes that this system helped her get 41+ million views in 30 days; that number is hers, from the post, not a result this page promises.
- Do not hire 50 bots. She is explicit: start with one job you already spend 30+ minutes on each week, then add.
- Create four bots with one job each: Content Lead, Writer, Reviewer, Publisher. Skills can be shared; publishing permission is not.
- If you use her public skill repo, import it with the "preserve instructions, tell me every change" prompt — she removed only Claude-specific
allowed-tools. - Put all four in one channel. Kick off a single real campaign. The Reviewer in her test graded a carousel 7/10 and sent it back; she approved; the Publisher queued it.
- Keep spend, send, and live posts behind your yes. Grok Bot was still in beta in her write-up — start with reversible work.
Why it works
The useful idea is not "AI will do my marketing." It is the org-chart discipline: one job per bot, a reviewer who is allowed to fail the writer, and a publisher who cannot see the hook library. She also names the bottleneck honestly — you were still opening every chat and pasting between tools. A shared channel plus approval gates is how a one-person company stops being twelve jobs with one human in the middle.
This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.