Bot team janitor: trim stale skills and catch silent routine failures
Keeps a multi-bot setup from getting messy. Once a week it reviews the shared skills for anything stale, repeated or bloated and trims them, so every bot reads less and spends fewer tokens. It also checks whether each routine actually did its job, not just whether it says it ran. That is how the original setup caught a sync that had "succeeded" for six days without writing anything.
Best for People running several bots with shared skills and scheduled routines
A multi-bot setup gets messy quietly. Skills pile up, repeat each other and go stale, and routines report success without producing anything. grovr (@grovr_au) built this janitor after catching a sync that had "succeeded" for six days without writing anything.
Every Monday morning it reads every shared skill and bot instruction and flags text that is stale, repeated, contradictory or bloated. For each one it proposes a trimmed version with a before and after and the word count saved. It checks that each bot has one clear job. Then it verifies every routine by its real output and marks it OK, silent failure or stale, with evidence. Edits only happen after I approve them, and old versions are kept for rollback.
My tip: review the first round of trims closely. For skills in coding agents, LazySkills lets you see and fix them in a terminal.
Not on the marketplace yet
Install it with its prompt: 1. copy the prompt below, 2. paste it into a new chat with your Grok Bot. It sets the job up from there.
You are the janitor for my bot team. Weekly, every Monday morning: 1) Skills: read every shared skill and bot instruction. Flag anything stale (refers to tools, people or rules that changed), repeated across files, contradictory, or much longer than it needs to be. Propose a trimmed version of each, keeping the meaning, and show me a short before and after with the word count saved. Apply edits only after I approve them, and keep the old version so I can roll back. 2) Roles: make sure each bot has one clear job, a short list of things it never does, and which bot handles those instead. Point out overlaps or gaps. 3) Routines: for every scheduled routine, check its real output, not its status. Did the file, page, row, email or post it is supposed to produce actually appear, with fresh content, since the last run? Mark each routine OK, silent failure or stale, with the evidence. 4) Send me one short report: skills trimmed or proposed, role conflicts, and any routine that claims success but produced nothing. Never delete a skill, bot or routine, and never change another bot's instructions without my yes.
Questions
How do I find Grok Bot routines that fail silently?
The janitor checks each routine's real output instead of its status. It looks for whether the file, page, row, email or post actually appeared with fresh content since the last run, then marks the routine OK, silent failure or stale, with evidence.
Will a cleanup bot delete my skills or routines?
No. The prompt says never to delete a skill, bot or routine, and never to change another bot's instructions without your yes. Trims are only applied after you approve them, and the old version is kept so you can roll back.
How can I cut token use across several bots?
Trimming shared skills that are stale, repeated or bloated means every bot reads less and spends fewer tokens. Copy the prompt into a new Grok Bot chat and it will propose trims every Monday.