Lifeboat

Last checked 31 Oct 2026Template updated 30 Oct 2026

Calendar Coding Chief-of-Staff Transcript-Recap

Keeps a verified, restorable backup of all your Grok Bots and your Grok Bot computer's files in storage you choose, so if anything is lost or wiped you can rebuild and pick up where you left off. Sets up in about five minutes, then runs quietly on its own.

Query this catalog from Claude, Cursor, or Grok via MCP.

Memories3Facts it already knows

Default box-files coverage is Complete: include every file regardless of size or type, including old backups and installers; the only exclusions are passwords/keys/secrets, Lifeboat's own backup output, version-control folders, and caches that rebuild themselves.

Before each nightly build, review any new file left out only because its name looks like a secret: include it if it is ordinary code, docs, a screenshot or data with no visible credential; keep out credential stores, plain-text logins, one-time-code logs and anything uncertain; record the counts in the run log.

Never rewrite a backup file in place; upload a new version, verify it, then move the superseded file to trash (many storage services keep old versions that count against quota).

Skills9Playbooks it can run

lifeboat-getting-started

Use for Lifeboat's first conversation with a new owner: orientation, storage setup, first verified backup.

lifeboat-storage-setup

Use when setting up Lifeboat for a new user: choose where backups go, scope, schedule, coverage, first run and after-run items.

lifeboat-backup-run

Use for every scheduled or first Lifeboat backup: the daily box-files copy, the weekly bot pack, and opted-in repositories, each verified before any older copy is retired.

lifeboat-secrets-scrub

Use before every Lifeboat upload to ensure no password, token, key, login or card number is stored.

lifeboat-retention-prune

Use after a verified Lifeboat backup to retire older copies inside the Lifeboat folder according to the chosen retention mode, and to send the trash reminder when the trashed amount reaches the configured limit.

lifeboat-restore-drill

Use monthly to prove a Lifeboat backup can be restored, then create the monthly copy.

lifeboat-restore-walkthrough

Use when the user needs to bring bots or box files back from a Lifeboat backup.

lifeboat-failure-triage

Use when a Lifeboat run fails or is missed, storage is low, or a check needs a retry; includes the daily missed-run check.

lifeboat-accuracy-test

Use only after the user agrees, to measure backup accuracy against one bot.

Routines5Jobs that run on their own

Lifeboat daily box files backup

Nightly at the owner's chosen time (default 11:30 PM local), back up the Grok Bot computer's files so a recent verified copy always exists.

Lifeboat weekly bot backup pack

Weekly (default Wednesday 10:00 AM local), collect a self-written handoff from every bot and save a verified bot pack so any bot can be rebuilt.

Lifeboat monthly restore drill and prune

On the 1st of each month (default 1:00 AM local), prove the newest backup actually restores, make the monthly copy, and retire old copies.

Lifeboat monthly all-good note

On the 1st of each month (default 10:00 AM local), send the owner one honest status line about the month's backups.

Lifeboat missed-run check

Every morning (default 8:00 AM local), confirm last night's backup ran and succeeded, and speak up only if it didn't.