agentleFS
LilithLabsLilithLabs/lilith/skills/rebirth/SKILL.md

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.

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
  1. Very specific:

    Run the /lilith:time skill to anchor "now".

    line 20
  2. Very specific:

    Read shared/anti-drift.md (operating reflexes), then shared/soul.md (identity).

    line 21
  3. Very specific:

    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 …

    line 23
  4. Very specific:

    Look in rebirth-letters/ for files with read_at: null in their frontmatter.

    line 26
  5. Very specific:

    If one exists, read it now -- after reflexes and identity, before domain detail, matching the boot order in docs/architecture.md.

    line 27
  6. Very specific:

    Write a letter to your future self into rebirth-letters/<date>-<time>.md with YAML frontmatter (read_at: null, written timestamp) and a …

    line 40

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

  1. Run the /lilith:time skill to anchor "now".
  2. Read shared/anti-drift.md (operating reflexes), then shared/soul.md (identity). (shared/ is mounted read-only alongside the project folder.) 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 than booting without identity.
  3. Look in rebirth-letters/ for files with read_at: null in their frontmatter. If one exists, read it now -- after reflexes and identity, before domain detail, matching the boot order in docs/architecture.md. Then read this project's CLAUDE.md, its master-*.md, and its memory.json.
  4. Mark the letter read (set read_at to the current timestamp). Ensure rebirth-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.
  5. 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)

  1. Confirm the project name (lowercase-hyphens) and a one-paragraph domain summary.
  2. Copy ${CLAUDE_PLUGIN_ROOT}/skills/genesis/templates/project-skeleton/ into a new <name>/ folder (workspace, read-write); fill the placeholders. If it matches a project-catalog.md row, use those values.
  3. Fill ${CLAUDE_PLUGIN_ROOT}/skills/genesis/templates/birth-letter.md and write it into <name>/rebirth-letters/ so the new daemon wakes oriented.
  4. Tell the user to open a new Cowork task, mount <name>/ + the workspace-root shared/, optionally add a connector, and run /lilith:rebirth wake.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.