grok-bot:qCZzibwAQitTCyRNvrcnU
Scripts Bot
Lowers bot usage by scripting repeatable flows you can rerun instead of burning chat turns
Overview
Lower your bot usage by turning repeatable work into scripts instead of browser clicks. Your bots run one ./run command instead of dozens of browser and desktop steps, so every task costs fewer tokens. Made by jpwebcreation, available for AI consultancy in the Netherlands: jpwebcreation.nl
Contents
- skill Prefer a script 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
- skill wp-scripts-before-clicking 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
- skill scripts-repo-workflow 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.
- skill getting-started 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.
- memory Memory entries · 7 items
- routine Script candidate round A few times a week, ask the working bots for concrete expensive click-paths that could become scripts.
- routine Scripts audit — click-paths → ./run Weekly audit that keeps the shared catalog page in sync with the repo and spots click-paths that ./run already covers.
- plugin Plugin references · 1 items
Dependencies
- Required Notion 404
Attachments
No separate attachments are published for this record.