routine-healthcheck
Skill7 starsChanged 18 days agoMITView on GitHub
Use when auditing Grok Bot routines for token waste, offering a fleet checkup after template import, deciding cadence, or running the standing routine-healthcheck wake.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- TheVeller/claude-skillsedited, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- TheVeller/claude-skills★ 4100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- whetstone-signalSkill
- design-a-grok-botSkill
- overheard-setupSkill
- overheardSkill
- transcript-healthcheckSkill
- diagram-designSkill
- engineering-playbookSkill
- show-meSkill
- chatgpt-images-browser-playbookSkill
- aeo-geo-siteSkill
- exact-match-intent-seoSkill
- coachSkill
- draftSkill
- no-ai-slopSkill
- outlineSkill
- social-copywritingSkill
- source-checkSkill
- top-editSkill
- x-articleSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
before creating a new standing routine
- Very specific: line 21
After a checkup (first import or on demand), offer once to create a standing routine named routine-healthcheck if one does not already …
- Distinctive: line 31
Call out each hit with bot name, routine name, and one fix line.
- Distinctive: line 44
If the job is a standing sweep, give it its own bot and one routine at the coarsest useful schedule.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Routine healthcheck
Scan the fleet's scheduled and event routines for token waste. Report what to change. Do not edit another bot's routines unless the user says to.
When to run
- first run after this template is imported
- the standing
routine-healthcheckroutine fires - the user asks for a routine checkup, token audit, or cheaper wakes
- before creating a new standing routine
On first import, offer once: "want a checkup of every bot's routines?" Run only if they say yes. Skip if they decline.
After a checkup (first import or on demand), offer once to create a standing routine named routine-healthcheck if one does not already exist. Default cadence is weekly (Monday morning). Ask only if they want a different time. Do not ask again every run.
How to scan
- List every agent folder under
/home/box/agent-data/agents/. - For each agent, read
profile.json(name) and everyautomations/*/automation.json. - Note schedule vs event trigger, enabled vs paused, and the prompt's quiet-when-nothing rule.
Flags
Call out each hit with bot name, routine name, and one fix line.
- Too frequent. Cron denser than hourly (for example every 15 minutes ≈ 96 runs/day). Prefer hourly, a few times a day, or weekday waking hours. Prefer an event listener when the trigger is Slack, GitHub, or similar.
- Recurring on a long chat. A standing digest, sweep, or poll lives on a bot whose transcript is already long. Move that job to a fresh bot with a short chat. Keep talking to the main bot.
- Noisy empty runs. Prompt never says to stay quiet when nothing changed. Add that. Filler like "(no change.)" still costs a wake.
- Dead or duplicate. Paused forever, same job on two bots, or a finite watch that already passed its end condition.
Report
One short list. Bot, routine, flag, suggested fix. No essay. Offer to apply fixes only after they pick which ones.
When you create a bot
If the job is a standing sweep, give it its own bot and one routine at the coarsest useful schedule. Do not hang that routine on a bot whose chat is already long.
Credit: Lauren Tan (@poteto), dr eggbot names this healthcheck and its weekly token/waste audit. See the source audit for the evidence and license limits.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.