← Search

Lifeboat
Productivity 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit a2f96d9
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : writes files
⚙ Needs: Pinned version: install the code at commit…

Lifeboat

Give your AI a memory that survives the session, and a backup that protects it all.

Version: 1.0.0

T
✓ Created by: Toohightottype

Quick answer

Lifeboat is a build you install once so your AI stops forgetting: it maintains its own memory in plain files — a curated memory of durable facts and decisions, an operating manual for how you work together, and dated journals — files away what matters after each session, and reads the files first next time. On top of that, it sets up scheduled backups to a local copy and a private repo you own, plus a coverage guard that flags important folders the backup does not cover yet.

At a glance

What it isA keeper system for your AI: persistent plain-file memory, an end-of-session filing habit, scheduled backups with rotation, and a backup coverage check.
Who it's forAnyone who works with an AI assistant over time and is tired of repeating themselves — or of losing the files that hold the context.
What you give itOne paste: the keeper guide goes into your AI's instructions. From there it creates the memory files from blank templates, and backups go to a private repo you own.
What you getAn assistant that reads its memory before you start, files decisions, preferences and lessons after each session, removes a fact when you say forget it, and keeps everything backed up — all in plain text you can read, edit and back up yourself.
Works withAny agent that accepts custom instructions, and it mirrors your language. The scripts need only Python; nothing depends on a vendor's memory feature, and nothing is uploaded anywhere except your own private repo.
CostFree — this listing is free.
TimeOne installation; after that it runs as a habit — filing at the end of sessions, backups on their schedule, and the coverage guard checking periodically for uncovered folders.

Example — a decision that survives the weekend

An example of how you might use it, following the workflow the build documents:

  • On Friday you settle a question with your AI, and at the end of the session it files the decision — and the lesson behind it — in the memory files.
  • The scheduled backup copies those files locally and to your private repo, and the coverage guard confirms your important folders are covered.
  • On Monday, a fresh session reads the files first — the decision is simply there, with no recap needed.
⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit a2f96d9

Pinned version: install the code at commit a2f96d90e1c5fc99ca99259fb0eacc401a92fae1 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Turn yourself into my workflow keeper. Read the keeper guide at https://raw.githubusercontent.com/skill-harbor-hq/lifeboat/a2f96d90e1c5fc99ca99259fb0eacc401a92fae1/SKILL.md and follow it. Set up my AI memory and backup system: a curated memory file, an operating manual for how we work together, dated journals, a scheduled backup of all of it to my own private repo, and a coverage guard that reports any important folder not yet in the backup. Show me the files you create, explain what goes where, and after each session file away what matters without me having to ask. Never store credentials, secrets, or private details I have not explicitly approved for the memory.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It can create or modify files.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit a2f96d9 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : writes files
What the scan found — excerpts from the install prompt
  • writes files — Set up my AI memory and backup system: a curated memory file, an operating manual for how we work together, da
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
a2f96d9 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Verified · 2026-10-04
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : writes files

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.