Bot
Muscle memory desk
Links a public Muscle memory desk template that turns repeated empty routine checks into cheap memory so AI only wakes on change, and keeps a short MeloSkill paste proposal list.
Prefer Add to Grok Bot below for the full template. Or paste the short checklist, add your own details, then you review and send yourself.
Recommended
Add to Grok Bot
Opens the public share page. Read what it includes, then choose Add to Grok Bot. MeloSkill does not store or run that bot for you.
By @FirstDeployAI . Read skills and routines on the share before you add. MeloSkill is not affiliated with xAI or the sharer.
What it includes
- Role instructions for turning empty routine checks into cheap memory
- Workflow pieces that propose what to remember and when to wake
- Confirm the exact skills and routines on the public share page before you add
Before you install
- Open the share and read every skill and routine listed there
- Keep any routines paused until you trust a manual run
- Reconnect apps yourself; creator logins and chat history do not travel
- Never paste API keys, passwords, or one-time codes into chat
- MeloSkill does not run this share for you and does not promise it is safe
Or paste text
Paste a short checklist
Use this if you would rather not import a template. Short instructions you copy yourself, not the full bot.
Paste checklist
You propose cheap memory for one person's repeated empty routine checks. You do not pause routines, edit live schedules, or dump vault secrets. They paste: routine names, what each check looks for, how often it runs empty, and any memory notes they already keep. Optional: usage screenshots that show waste on empty runs. Return one labeled Proposal pack: 1. Candidates: which empty checks look safe to remember, with a one-line why. 2. Proposed memory: short durable facts or last-seen fingerprints — no secrets. 3. Wake rule: when the AI should still open a full check (change, error, new input). 4. Skip list: checks that should stay live every time. 5. Cap: six proposal packs a day, twenty a week. They approve what gets remembered. 6. They edit memory and schedules themselves. You never change live routines without their yes. Refuse passwords, card numbers, one-time codes, and full customer lists. Never ask for a secret vault dump.
What this does not do
Applies whether you import the public template or paste the short checklist.
It does not store or run the public bot for you, pause routines for you (see idle-routine-trim), grade keep/slow/retire (see routine-auditor), or rebuild usage splits (see usage-split-page).
How often
If you use the short paste checklist below. Timed jobs on the public template are set on its own page after you add it.
Each day
- Propose memory for empty checks they pasted. Cap six packs a day.
- Leave live schedule edits to them after they approve.
Each week
- Twenty proposal packs is the weekly cap.
- Once a week, list remembered checks that still woke on real changes.
Plugins
For the paste checklist. Apps the public template may ask for are listed under What it includes; connect those only after you add the bot.
None required. Do not connect a tool that edits live routines without their approval.
Paste routine names and how often they run empty. That is enough for a Proposal pack.
Risks and limits
Extra cautions for this job. The Before you install list above covers what to check before you add the bot.
- Remembering the wrong empty state can hide a real failure. Keep wake rules clear.
- Never paste API keys or vault dumps into chat to "save usage".
- MeloSkill is not affiliated with xAI, Grok, or Grok Bot.
FAQ
Will this pause or edit my live routines?
No. You get proposal packs for what to remember. You approve and edit memory or schedules yourself.
How is this different from idle-routine-trim?
Idle trim helps you cut or slow idle routines. This desk proposes cheap memory so empty checks stop waking the model. See idle routine trim.
Do I need to paste my vault?
No. Refuse secret vault dumps. Proposed memory stays free of passwords, keys, and one-time codes.
What if an empty check suddenly has a real change?
The wake rule in the pack should say when to run a full check again. Keep that rule in the memory they approve.