agentleFS
Sign inStart free
LilithLabsLilithLabs/lilith/skills/tutorial/SKILL.md

tutorial

Skill1 starsChanged 5 months agoMITView on GitHub

Guided, friendly walk-through of Lilith for new (especially non-technical) users. Use when the user says "/lilith:tutorial", "walk me through it", "how do I use this", "teach me", "I'm new", or is stuck on setup -- especially on the step of opening a project in its own Cowork task. Owns the highest-friction onboarding moment.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    update

    Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not dump everything at once.

    line 16
  2. Very specific:

    If they have not run /lilith:genesis, hand off to it.

    line 27
  3. Very specific:

    When you want a SECOND domain -- say finance AND household -- that is when Lilith becomes a staff, and each domain gets its own Cowork task …

    line 38
  4. Distinctive:

    Add your mail or calendar connector if it needs one.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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

Tutorial

Walk the user through Lilith one small step at a time, checking in after each. Do not dump everything at once.

Part 1 -- The idea (60 seconds)

Lilith is a staff, not a chatbot. A Chief of Staff (Prime) coordinates project daemons, each owning a domain. She remembers across sessions and watches your documents and deadlines. Your files stay in local folders here -- Lilith runs no cloud of its own (what it reads is processed by the model it runs on, like any AI assistant).

Part 2 -- Setup

If they have not run /lilith:genesis, hand off to it. If they have, continue.

Part 3 -- Your first project, the easy way

For the first project there is no multi-task machinery to learn. Work with it right here, in the same place genesis set you up. Drop the documents it asks for (see WHAT-TO-DROP-HERE.md), say "read these," and you are going. Get a win first -- nothing fancy.

Part 4 -- Growing into a family (when you're ready)

When you want a SECOND domain -- say finance AND household -- that is when Lilith becomes a staff, and each domain gets its own Cowork task so they don't bleed into each other. To bring a new one to life, one step at a time:

  1. Open a new Cowork task (new chat/workspace).
  2. Mount that project's folder AND the workspace-root shared/ folder.
  3. Add your mail or calendar connector if it needs one.
  4. Type /lilith:rebirth wake.

/lilith:rebirth wake reads the welcome letter left for that project, so it wakes up already knowing its job. It gets easy after the first time. (Create new domains anytime with /lilith:rebirth birth.)

Part 5 -- When you forget the ritual (you will, and that's fine)

Lilith recovers gracefully. The three most common slips and the fix:

  • "It doesn't seem to know who it is / I see the wrong project." You probably mounted the wrong folder, or an extra one. Mount only this project's folder + shared/, and re-run /lilith:rebirth wake.
  • "It forgot what we were doing." You likely opened the task without /lilith:rebirth wake. Just run it -- it reads the handoff letter and re-orients.
  • "Its memory feels cluttered or out of date." Run /lilith:consolidate-memory -- it tidies and reconciles, and tells you what changed.

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.

Check your setup, free