When you look after a handful of client sites, the work you want from an agent is usually the same on every one: the weekly report, the content check, the shop tidy-up. Playbooks make that repeatable, and since each site keeps its own copy, a small difference between copies can slip in unnoticed.
Run one read-only playbook across every connected site, check the copies match, and get one table at the end.
I manage several sites and want the same read-only playbook run on each.Do not change anything on any site.
For each site you are connected to, in turn:1. Confirm the site name and URL, and label everything below with it.2. List the Active playbooks and find [Weekly content report]. If it is missing, say so and move to the next site.3. Load it. Note its last updated date and whether its steps match the copy on the first site. If they differ, quote the differing lines.4. List any of its tools this connection cannot use.5. If the connection reports it is paused, note "paused" and move on.6. Run the playbook. Skip steps whose tools are unavailable, with a note. If any step would write, skip it and tell me.
Then give me one table with a row per site: site, playbook found (yes orno), copy matches (yes or no), tools unavailable, and the headline resultfrom the playbook's own report. Put the full per-site reports below it.Why this is safe to run
The prompt keeps to reads and tells the agent to skip any step that would write, so a playbook that turns out to have a write step does nothing on any site. Each site is checked against its own connection, which means each site’s switches, access preset and role apply separately. What one connection can do says nothing about the next.
Playbooks live on each site, so the copy on the third client site may still be last quarter’s. Quoting the lines that differ tells you which site to update on its Playbooks tab.
Already connected to your sites? Ask your agent to run your playbook on every site and compare, and keep it to read-only playbooks.