agentleFS
Sign inStart free
mhmarkhoffmann-lobmhmarkhoffmann-lob/claude-desk/skills/last/SKILL.md

last

Skill0 starsChanged 5 months agoMITView on GitHub

Session start: shows what ran last and all active projects. Loads the last project's FOCUS.md — ready to act immediately. Trigger on: "/last", "what did we do last?", "continue", "session start", "where were we?", "weitermachen", "wo waren wir".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

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

    Read {{BRAIN_ROOT}}/CHANGELOG.md and take the newest entry — derive the last active project from it.

    line 18
  2. Very specific:

    Read {{BRAIN_ROOT}}/BRAIN.md.

    line 33
  3. Distinctive:

    If no FOCUS.md exists: print the project status from BRAIN.md and tell the user

    line 44

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

Last Session — Session Start

Base path for all files below: {{BRAIN_ROOT}} (set by install.sh).

Steps

Step 1: Find the last project from CHANGELOG

Read {{BRAIN_ROOT}}/CHANGELOG.md and take the newest entry — derive the last active project from it.

Step 2: Load that project's FOCUS.md

Resolve the path dynamically (do not hardcode a project list):

  • List directories under {{BRAIN_ROOT}}/projects/*/ and match the project name from the changelog entry against folder names.
  • Read {{BRAIN_ROOT}}/projects/<category>/<project>/FOCUS.md.

Step 3: Output FOCUS.md

Print the full FOCUS.md content — no comment, no intro. Then a divider: ---

Step 4: Read BRAIN.md and list all active projects

Read {{BRAIN_ROOT}}/BRAIN.md. List every project under "Active". Format per project: Name — one-line status (verbatim from BRAIN.md, do not interpret).

Step 5: Closing question

"What do you want to work on — continue with [last project] or pick another?"

Rules

  • FOCUS.md: no comment, no intro — output exactly as written
  • If no FOCUS.md exists: print the project status from BRAIN.md and tell the user
  • Projects: active only, no inactive or archived
  • A single follow-up question at the end

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