agentleFS
ImtylerrrrrrImtylerrrrrr/second-brain/skills/start-session/SKILL.md

start-session

Skill1 starsChanged 5 months agoMITView on GitHub

Resume work from the second-brain — vault dashboard brief plus the per-repo thread (what happened last, what is next) with a mechanical staleness check. Use at the start of a working session.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only. Restores context.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 7 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

second-brain: start-session

Read-only. Restores context; writes nothing.

Steps

  1. Locate the vault (cwd or ancestors containing Projects/Dashboard.md; else registered vaults in ~/.claude/second-brain/vaults, ask if several). None → "run /second-brain:setup first."
  2. Vault brief from Projects/Dashboard.md + Projects/_AUTO_status.md, tersely:
    • 🔴 blocked / ⏰ deadline rows first
    • 🟢 active rows: Last session + Next from the Dashboard
    • dirty worktrees from _AUTO_status.md worth committing
  3. Repo thread — if the user named a repo or cwd is inside one, read Projects/<repo>.md and restore:

    Last handoff (@last_handoff_commit): <Last: content> Next (intent): <Next: content>

  4. Mechanical drift check for that repo:
    • git -C <repo> log --oneline <last_handoff_commit>..HEAD → N commits since handoff. N>0 → "⚠️ N commits since last handoff:" + subjects; the recorded thread may be stale.
    • last_handoff_commit: none (auto-stub) → "never handed off yet — onboard with /second-brain:analyze <repo>."
    • Note contradicts git facts (branch mismatch, note claims work git doesn't show) → say so and recommend /second-brain:analyze. Never silently trust a stale note.
  5. End with: "Pick up where you left off — <Next intent>?"

Rules

  • Writes nothing. Missing/stale notes → recommend the right command, don't fix here.

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.