agentleFS
GerardoRdz96GerardoRdz96/aios-starter-kit/.claude/skills/session-handoff/SKILL.md

session-handoff

Skill3 starsChanged 5 months agoMITView on GitHub

Use when the user wants to wrap up, clear context, switch machines or tools, or continue work in a fresh session — "hand off", "wrap up this session", "save where we are", "I need to clear context", "write a handoff", "/session-handoff". Prints and saves a structured handoff note (what we did, files touched, open decisions, next steps) so the next session — in any tool — can pick up exactly where this one left off.

149 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, research-fleet and 8 more.

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.
  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • SethGammonSkill

    research-fleet

    Parallel research using Fleet wave mechanics. Spawns multiple scout agents, each investigating a different angle of the same question. Findings are compressed between waves. Produces a unified research brief from multiple independent perspectives.

    Also in 3 projects that use this

  • vicoa-aiSkill

    live-preview

    Start a local app in the current user project, expose it through a tunnel, and return preview details in structured Markdown. Use when the user asks for a preview URL, public URL, shareable localhost, mobile/web preview, or tunnel setup.

    Also in 4 projects that use this

  • Dizzy-TenSkill

    bug-diagnosis

    Diagnose bugs and product issues without modifying code. Use when the user explicitly invokes $bug-diagnosis or asks for diagnosis, root-cause analysis, issue classification, or fix strategy for code bugs, failing tests, configuration/dependency problems, deployment issues, performance regressions, data anomalies, or frontend/user-experience problems described through screenshots, annotations, logs, errors, or natural-language reports. Prioritize analysis and recommendations only; do not edit files.

    Also in 4 projects that use this

  • botlearn-aiSkill

    doc-gen

    Also in 4 projects that use this

  • flyingobsidianSkill

    terminology

    Read a codebase, find terminology, create/update definitions into a markdown document.

    Also in 3 projects that use this

  • +1 more from SethGammon

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 127 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If any item belongs in pending.md (a follow-up that would otherwise be lost), append it there too and say so.

    line 45
  2. Distinctive:

    Keep it under a page. The next session needs orientation, not a transcript.

    line 50

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

What this skill does

Generates a handoff note for the current session: a single markdown block that a fresh session (or a different AI tool entirely) can read to continue the work without re-deriving anything. This is the cheapest insurance an AIOS has against context loss.

Pattern credit: Nate Herk's session-handoff skill — "if you keep retyping the same prompt, that's a skill."

When to fire

  • The user says they're done for now, switching tools (Claude Code ↔ Cowork ↔ another CLI), or context is getting full.
  • Proactively offer (one line, don't insist) when a long session is clearly winding down.

The handoff template

Produce this, filled in from the actual session — concrete file paths, not vague summaries:

# Session handoff — {date} — {topic}

## What we did
- {completed item, with file paths}

## Files created / changed
- {path} — {one-line what/why}

## Open decisions (waiting on the user)
- {decision} — options considered: {...}

## In progress / next steps
1. {next concrete action, specific enough to start cold}

## Gotchas for the next session
- {anything surprising: a failing test, a quirk found, a constraint}

Where it goes

  1. Print it in chat (always — the user may just copy it).
  2. Save it to knowledge/handoffs/{YYYY-MM-DD}-{slug}.md (create the folder if needed). This is a deliberate exception to the "knowledge/ is immutable raw source" rule: a handoff is a local, gitignored operational record of this session, not a fact that graduates into references/. Keep handoffs/ out of version control so private session notes never get committed.
  3. If any item belongs in pending.md (a follow-up that would otherwise be lost), append it there too and say so.

Guardrails

  • Report honestly: if something is half-done or broken, the handoff says so. A flattering handoff is a useless handoff.
  • Keep it under a page. The next session needs orientation, not a transcript.

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.