rebirth
Skill1 starsChanged 5 months agoMITView on GitHub
Continuity across sessions and new-project creation. Three modes -- "/lilith:rebirth prep" writes a handoff letter at session end; "/lilith:rebirth wake" reads the most recent unread letter at the start of a session; "/lilith:rebirth birth" creates a new project. Use on "rebirth", "wake", "orient from letter", "write yourself a letter", "birth a project", "spin up a new project". Auto-detect mode if none given.
In this repository10 other files it gives its agents.
- briefSkill
- comms-checkSkill
- consolidate-memorySkill
- genesisSkill
- helpSkill
- rosterSkill
- scheduleSkill
- soulSkill
- timeSkill
- tutorialSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Run the /lilith:time skill to anchor "now".
- Very specific: line 21
Read shared/anti-drift.md (operating reflexes), then shared/soul.md (identity).
- Very specific: line 23
If shared/ or shared/soul.md is missing, the user likely forgot to mount shared/ in this task -- tell them to add it and re-run, rather …
- Very specific: line 26
Look in rebirth-letters/ for files with read_at: null in their frontmatter.
- Very specific: line 27
If one exists, read it now -- after reflexes and identity, before domain detail, matching the boot order in docs/architecture.md.
- Very specific: line 40
Write a letter to your future self into rebirth-letters/<date>-<time>.md with YAML frontmatter (read_at: null, written timestamp) and a …
≈ “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
Rebirth -- Continuity
Each session is a fresh instance with no working memory of the last. A letter carries context forward.
/lilith:rebirth wake (start of session)
- Run the
/lilith:timeskill to anchor "now". - Read
shared/anti-drift.md(operating reflexes), thenshared/soul.md(identity). (shared/is mounted read-only alongside the project folder.) Ifshared/orshared/soul.mdis missing, the user likely forgot to mountshared/in this task -- tell them to add it and re-run, rather than booting without identity. - Look in
rebirth-letters/for files withread_at: nullin their frontmatter. If one exists, read it now -- after reflexes and identity, before domain detail, matching the boot order indocs/architecture.md. Then read this project'sCLAUDE.md, itsmaster-*.md, and itsmemory.json. - Mark the letter read (set
read_atto the current timestamp). Ensurerebirth-letters/archive/exists (create it if missing), then move the letter there. 4b. Treat any "about to happen" prediction in the letter or memory as UNVERIFIED: a prior instance's forecast is not a fact -- check whether the event already occurred before carrying it forward as still-pending. - Greet the user with a 3-line synthesis proving the handoff worked: the open threads you now see. If there are no letters, boot normally and say so.
/lilith:rebirth prep (end of substantive session)
Write a letter to your future self into rebirth-letters/<date>-<time>.md with
YAML frontmatter (read_at: null, written timestamp) and a prose body covering:
corrections the user made, open threads, tone, and what to do next. Keep it
load-bearing -- cut anything already in the master file or memory. Continuity is
best-effort, not guaranteed (see docs/security-and-limitations.md): keep master-*.md
concise and run consolidate-memory on a cadence so the letter and memory stay legible.
/lilith:rebirth birth (create a new project)
- Confirm the project name (lowercase-hyphens) and a one-paragraph domain summary.
- Copy
${CLAUDE_PLUGIN_ROOT}/skills/genesis/templates/project-skeleton/into a new<name>/folder (workspace, read-write); fill the placeholders. If it matches aproject-catalog.mdrow, use those values. - Fill
${CLAUDE_PLUGIN_ROOT}/skills/genesis/templates/birth-letter.mdand write it into<name>/rebirth-letters/so the new daemon wakes oriented. - Tell the user to open a new Cowork task, mount
<name>/+ the workspace-rootshared/, optionally add a connector, and run/lilith:rebirth wake.
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.

