← Back to library
MarketingWorkflow

Get a daily blog health report from a scoped bot role

In a long Grok Bot guide, Flavio Copes designs Blog Pulse, a daily reviewer for his site. Its role names the analytics, hosting, repository and live-site sources, lists seven checks, requires facts kept apart from interpretation, saves a Markdown report and forbids publishing, pushing, emailing or buying without approval. Missing sources are recorded, never guessed.

  • OutcomeReceive a dated report each morning confirming the scheduled post went live, comparing traffic, listing top pages and checking the last deploy, with every claim sourced.
  • SetupUnder an hour
  • LevelStarter
  • CreditFlavio Copes
View original
Works with
Grok Bot

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You publish on a schedule
  • You check analytics and deploys by hand
  • You want a bot with clear limits

Not for: Sites without analytics or deploy logs; Anyone wanting the bot to publish for them

What do you need, and what do you get?

You need

  • Analytics dashboard access
  • Hosting deployments page
  • The repository and live site

You get

  • A dated Markdown report
  • Traffic comparison and top pages
  • Suggested next actions

How does it work, step by step?

  1. Answer six questionsState what outcome it is responsible for, where it may look, which tools it may use, the report shape, what needs sign-off and how to handle gaps.
  2. Layer the instructionsPut fixed safety rules, the standing duty and this week's priority in separate sections.
  3. List the checksPost live, visitors versus the weekly average, top pages, deploy status.
  4. Require evidenceAsk for sources on every claim and a split between facts and interpretation.
  5. Connect narrowlyPrefer a plugin, then an API, then the browser, and only then the local computer.

The prompt

Our own prompt, inspired by Flavio Copes and written to work in Grok Bot. Values in lime are placeholders.

Prompt0 variables
You are the daily reviewer for [site]. Use [analytics], [hosting deploys page], [repo] and the live site. Each morning: confirm the scheduled post is live and link it; set yesterday's traffic against the trailing week; name the five busiest pages and where visits came from; check the last deploy. Separate facts from interpretation and link every claim. Save as reports/[date].md. Do not publish, push, send or buy anything. If a source fails, record it and continue.

Inspired by Flavio Copes: A deep dive into Grok Bot. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Words like brilliant or proactive do not define work; specify sources and stopping rules instead.
  • The product is in beta, so check current plans before paying.

Our take

Flavio Copes's Blog Pulse role template is the reusable asset: named sources, a fixed list of checks, a hard split between facts and interpretation, a known output location and clear limits, with no vague adjectives. Requiring that missing sources be recorded rather than guessed stops the report from inventing analytics when a connector fails. We would add a short what-I-could-not-check line at the top so a failure is impossible to miss when skimming. Keep the daily Markdown files; a month of them makes trend questions easy to answer without reopening dashboards. Forbid publishing, pushing, emailing or buying without approval, exactly as his role does, so a health check never becomes an autonomous publisher. Connect only the analytics, hosting and repository accounts it needs. The same structure works for a shop, a newsletter or a product dashboard: change which inputs and checks you list, keep the evidence rules. Review the first week of reports line by line before trusting them on autopilot.

Where the time goes back: Several dashboards are checked in one pass, and you only read the exceptions.

FAQ

What can the bot do on its own?
Look at linked tools and draft material; publishing, pushing and sending need approval.
What if analytics is down?
It records the missing source and continues with the other checks.

Source and credit

Inspired by Flavio Copes. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
A deep dive into Grok Bot
Creator
Flavio Copes
Published on
flaviocopes.com
Original date
Aug 22, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok Bot
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.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingWorkflow✓ AI dry run

Run research-to-publish agents under a chief of staff

Run research, planning, writing and publishing as a coordinated set of agent roles, led by a coordinator and backed by a memory role and a verification step before anything ships.

Credit: Morlex (@0xMorlex)

An afternoon+
MarketingWorkflow✓ AI dry run

Build a context repo that runs a paid-ads agency's work

Let one project manager run client ads, reporting and onboarding by giving Claude Code a structured knowledge folder and task-specific skills.

Credit: Victor Chazarra

An afternoon+
MarketingPrompt✓ AI dry run

Explain a business process with a short animated walkthrough

Turn the documents that describe one of your processes into a short, vertical animated explainer for investors, new hires or clients, with every on-screen claim traced back to a file.

Credit: Avi Hacker, J.D.

Under an hour
MarketingPrompt✓ AI dry run

Offer an editor a working page for a dead link

Confirm which outside links in your niche are truly dead, check whether your page fills the same role, and get a short factual note to the editor for each real match.

Credit: Kourosh Ghaffari (@BuildingWaves)

Under an hour