When should you use it?
- Agents draft or schedule your social posts
- An automation can change ad budgets
- You want fewer off-brand posts
Not for: Accounts with no human reviewer at all; Ad platforms where you cannot set account-level limits
What do you need, and what do you get?
You need
- Brand rules and examples
- Scoring rubric
- Ad account limits
You get
- Scored drafts with block, review or publish decisions
- Spend alerts
How does it work, step by step?
- Write the rubricDefine what earns points: accuracy, brand voice, clear offer, no unsupported claims.
- Set three bandsChoose thresholds for blocked, needs review and allowed; start strict.
- Score every draftHave a separate reviewer prompt score drafts against the rubric with reasons.
- Cap spend at the platformSet daily and lifetime limits in the ad account itself, not only in the agent.
- Review the bands monthlyCheck what slipped through and tighten the rubric.
The prompt
Our own prompt, inspired by u/ProbablyCh on r/buildinpublic and written to work in Claude, ChatGPT and n8n. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Score this draft post from 0 to 100 against the rubric: {rubric}. Brand rules: {brand_rules} Draft: {draft} Return: score, one line per rubric item with reasons, any claim that needs a source, and a decision (BLOCK under {low}, REVIEW under {high}, else ALLOW).
Inspired by u/ProbablyCh on r/buildinpublic: I already spent 2 months on this AI Marketing Agents tool. Is this worth it?. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A model grading its own draft is lenient; use a separate reviewer prompt.
- Agent-side budget checks fail silently; platform limits are the backstop.
Our take
Most multi-agent marketing setups skip the boring part this author lost sleep over: what stops the agent from publishing junk or overspending at three in the morning. A scored gate plus platform-level spend limits is the most reusable piece of the post. Keep the auto-publish band empty until you trust the scorer. Write the rubric in plain language and calibrate it on past good and bad drafts. Set three bands: block, human review, allow. Cap spend at the ad platform itself, not only in the agent prompt. Review the bands monthly against real performance. Log every blocked draft so you can see whether the scorer is too harsh. Separate brand-safety checks from engagement scores. Never let the agent raise its own ceilings. Alert a person when spend approaches the cap. Require two consecutive good weeks of scored drafts before widening the allow band at all. Mirror the same ceilings inside the ads manager UI so a prompt bypass cannot overspend.
Where the time goes back: Low-quality drafts are stopped automatically, so review time goes to the borderline ones.
FAQ
Should anything auto-publish?
Where do the thresholds come from?
Source and credit
Inspired by u/ProbablyCh on r/buildinpublic. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I already spent 2 months on this AI Marketing Agents tool. Is this worth it?
- Creator
- u/ProbablyCh on r/buildinpublic
- Published on
- Original date
- Mar 28, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.