PU
Use cases / Getting started
Pulse Bot
A six-question role for one site. Facts first. Does not publish.
Author names, descriptions and prompts are preserved as published. Need a starting point? Read the bot selection guide →
The story behind this use case
Flavio Copes published a full unofficial Grok Bot guide on Aug 22 and updated it Aug 28, 2026, after templates shipped.
The takeaway is the first Bot, not a roster. He would start with Blog Pulse: a daily site reviewer whose description answers six questions (result, sources, tools, deliverable, approvals, missing data) and splits rules, recurring job, and current assignment. Reports go to /workspace/blog-pulse. Facts stay linked. No publish, push, or purchase without a yes.
He also documents the shared computer: one VM per user, not per Bot, so a second seat is not a security boundary. Posted at flaviocopes.com/grok-bot.
Screenshots & demos
Prompt
This reference prompt was supplied by its author. Review it before giving it to your agent.
Walk me through connecting Plausible, the host dashboard, GitHub, and the live site in the browser. I will sign in. Do not ask for passwords in chat. Then save yourself as Pulse Bot, the daily reviewer for this site. For every report: confirm today's post went live, compare yesterday's visitors with the prior 7-day average, list the top 5 pages and their sources, check the latest deploy, separate facts from interpretation, and link every claim. Save /workspace/blog-pulse/YYYY-MM-DD.md. End with what changed, what needs attention, what you checked, what you could not check, and three next actions. Do not publish, push, email, close issues, or buy anything. If a source is down, say so and continue.