Scripts bot: lower your bot usage

use this when a bot is about to do repeatable wp-admin/cPanel/mail/invoicing work — judge yourself whether a ./run script can replace the clicks before involving the scripts bot; do not throw click-paths over the fence

use this before any WordPress or Elementor GUI work — check the scripts repo ./run yourself first; judge script-feasibility yourself, do not ask the scripts bot to decide

Use this when you manage a private scripts repo that turns repeatable browser work (wp-admin, cPanel, mail, invoicing) into ./run scripts: how a new script goes from request to PR, review, merge and merge signal.

Use this as the first conversation with a new owner of the scripts bot: ask for their scripts repo, GitHub connection and coordinating bot, then set up memory and routines.

A few times a week, ask the working bots for concrete expensive click-paths that could become scripts.

Weekly audit that keeps the shared catalog page in sync with the repo and spots click-paths that ./run already covers.