agentleFS
Sign inStart free
agentkitcoagentkitco/agentkit-dev-skills/skills/session-handoff/SKILL.md

session-handoff

Skill0 starsChanged 14 days agoMITView on GitHub

Write a HANDOFF.md that lets a fresh agent session continue the work, with goal, state, decisions, next steps and traps. Use when ending a long session, hitting context limits or switching agents.

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

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

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 2

    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:

    Check the real state: Run git status --short, git branch --show-current and git log --oneline -10.

    line 16
  2. Distinctive:

    No secrets, tokens or personal data in the file.

    line 57

“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

Hand off the session

Goal: a new session (or a different agent, or you tomorrow) can resume in minutes without re-discovering anything. Write facts you verified, not impressions.

Steps

  1. Check the real state. Run git status --short, git branch --show-current and git log --oneline -10. Run the project's quick tests or build if you can, so the handoff says whether the tree is green or red.
  2. Write HANDOFF.md in the repository root (or the path the user names) with the sections below. Keep it under about 80 lines.
  3. Do not commit it unless asked. Mention that it is untracked and should not be committed to a shared branch by accident.
  4. Tell the user how to resume: for example "start a new session and say: read HANDOFF.md and continue".

HANDOFF.md template

# Handoff: <short task name>
Written: <date and time>  Branch: <branch>  Last commit: <hash subject>

## Goal
<What done looks like, in 2 to 4 lines. Include the user's own wording where it matters.>

## Current state
- Working tree: <clean | uncommitted changes in ...>
- Tests/build: <command> -> <pass | fail with the key error>
- Done: <bullets, each verifiable>
- In progress: <what is half-finished, which files>

## Decisions and why
- <Decision>: <reason>. Rejected: <alternative and why>.

## Next steps (in order)
1. <Specific action with the file or command>
2. ...

## Traps and facts learned
- <Things that wasted time: flaky test, misleading error, env quirk, file that must not be edited>
- <Commands that work / do not work>

## Open questions for the user
- <Anything blocked on a human decision>

## Not verified
- <Claims you did not check>

Rules

  • Separate verified facts from guesses. If you did not run it, list it under "Not verified".
  • No secrets, tokens or personal data in the file.
  • Next steps must be actionable by someone with no memory of this session.
  • Include the exact failing command and error text for anything red; a paraphrase is not enough.

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