agentleFS
Sign inStart free
zedarvateszedarvates/frugal-skills/skills/session-handoff/SKILL.md

session-handoff

Skill1 starsChanged 31 days agoMITView on GitHub

Instructions for the upstream workflow: Create, validate, and render a bounded provider-neutral session brief without storing raw transcripts or secrets. Use before switching model, agent, host, or context window.

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, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 117 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:

    Default maximum: 16 KiB, measured on the emitted UTF-8 JSON.

    line 42

“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 — portable continuation without hidden state

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

session_handoff captures the minimum verified state needed by another coding agent. It is local, stdlib-only, and explicit that the receiving agent gets a brief, not the original provider session.

python -m skills.session_handoff.cli create `
  --goal "Finish the targeted change" `
  --summary "Implementation is present; targeted tests remain" `
  --completed "Added the bounded contract" `
  --next-step "Run the targeted tests" `
  --evidence "file=skills/session_handoff/handoff.py" `
  --source-agent codex `
  --output .botte/handoff.json

python -m skills.session_handoff.cli validate .botte/handoff.json
python -m skills.session_handoff.cli render .botte/handoff.json

The same contract is available through the lazy session_handoff MCP tool. Its create, validate, and render actions exchange JSON objects only; MCP does not read or write handoff files. Use find_tool("session handoff") to load the schema without adding it to the always-on tool prefix.

Contract

  • Schema: botte-session-handoff-v1.
  • Default maximum: 16 KiB, measured on the emitted UTF-8 JSON.
  • Continuation mode: always brief_only; no cross-provider resume claim.
  • Git capture: branch, full object id, dirty flag, and relative changed paths; inspection is read-only and no absolute workspace path is stored.
  • Privacy: unknown fields, probable secrets, and raw transcript fields fail validation. Prompts, responses, environment variables, and terminal history are never collected automatically.
  • Safety: an active brief needs a next step; a blocked brief needs a blocker.

The upstream skill cites Traycer's durable-metadata and no-transcript design concepts. Its referenced provenance plan is not supplied or independently verified here; see the open entry in this catalog's THIRD_PARTY_NOTICES.md. Do not treat that citation as verified licence evidence or assume an external implementation is bundled. Check the installed handoff contract before asserting its privacy properties.

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