agentleFS
Sign inStart free
trac3r00trac3r00/agent-skills/skills/session-handoff/SKILL.md

session-handoff

Skill0 starsChanged 3 months agoMITView on GitHub

Carries work context between AI agent clients. Reads session logs from every installed client's native store (Claude Code JSONL projects, Codex rollout JSONL, OpenCode SQLite, Gemini CLI chats), and produces a portable handoff briefing — what was asked, what was done, files touched, last state — so a session in one client can continue work started in another. Use when switching clients mid-task ("bring everything I worked on in Codex into this Claude session"), resuming after days away, or auditing what any client did recently.

139 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ascii-diagram, research-fleet and 10 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

  • 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

  • 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 3 projects that use this

  • +1 more from SethGammon

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 0

    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:

    All commands accept --json for machine-readable output.

    line 28

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

Session Handoff

One machine, many agent clients, one work history. session_handoff.py reads each client's native session store read-only and turns recent work into a briefing the current client can consume.

Commands

python3 scripts/session_handoff.py list                       # recent sessions, all clients
python3 scripts/session_handoff.py list --cwd $(pwd)          # only sessions about this project
python3 scripts/session_handoff.py show claude:a3f7e0b9       # one session's turns + files
python3 scripts/session_handoff.py handoff --cwd $(pwd)       # markdown briefing to stdout
python3 scripts/session_handoff.py handoff --since 7 --sessions 8 --out HANDOFF.md

All commands accept --json for machine-readable output.

Typical flow

You worked in Codex yesterday; today you open Claude Code (or any client) and ask it to continue:

  1. handoff --cwd <project> produces the briefing: per session, the user asks, the last assistant state, and the files it touched.
  2. Paste the briefing (or --out HANDOFF.md and reference the file) into the current session.
  3. The current agent reads it and picks up where the other client stopped.

An agent running this skill should execute step 1 itself and ingest the output directly instead of asking the user to paste it.

Session stores read (read-only, local, nothing uploaded)

ClientStoreFormat
Claude Code~/.claude/projects/<slug>/*.jsonlJSONL events (user/assistant/tool_use)
Codex~/.codex/sessions/**/rollout-*.jsonlJSONL (session_meta, response_item)
OpenCode / OMO~/.local/share/opencode/opencode.dbSQLite (session, message, part)
Gemini CLI~/.gemini/tmp/<hash>/chats/*.jsonJSON chat logs

Missing stores are skipped silently. Command/hook noise (slash-command wrappers, task notifications, skill-load banners) is filtered so the briefing holds real work, not harness chatter.

Semantics

  • --cwd matches sessions whose working directory is the target or inside it (never a parent — a session about ~ is not a session about your project).
  • show <provider>:<id-prefix> resolves any unambiguous id prefix.
  • The OpenCode reader also covers OMO/Senpi sessions (same store).
  • Older sessions: raise --since (days); list searches up to a year for show resolution.

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