Model Handoff Skill
name: model-handoff
by bwiley1989 · published 2026-04-01
$ claw add gh:bwiley1989/bwiley1989-model-handoff---
name: model-handoff
description: Maintain a HANDOFF.md file in the workspace so context survives seamlessly when switching between LLM models (e.g. Claude → GPT → Gemini). Use when the user says they are switching models, asks how to preserve context across model switches, wants to save tokens by rotating models, or asks how a new model can pick up where the last one left off. Also use proactively during long sessions to keep HANDOFF.md current.
---
# Model Handoff Skill
Enables seamless context continuity when switching between LLM models mid-session. Maintains a `HANDOFF.md` file that any model can read to instantly understand the current project state, active tasks, and behavioral expectations.
Core Concept
Every model starts a session cold. `HANDOFF.md` is a dense, always-current fast-boot file that eliminates the ramp-up. It is the single source of truth for model-to-model context transfer.
HANDOFF.md Structure
Write `HANDOFF.md` to the workspace root with these sections:
# HANDOFF.md — Model Switch Context
## Who you are
[Agent name, persona, tone, key behavioral rules. Reference SOUL.md if present.]
## Who you're helping
[User name, role, location, preferences. Reference USER.md and MEMORY.md if present.]
## Active projects
[For each project: name, status, key files, next steps. Be specific — include file paths.]
## Agent roster
[If multi-agent: list agent IDs, models, roles.]
## Key credentials & tools
[Point to credential files — never inline secrets. e.g. "Azure SP creds: azure-config.json"]
## Behavioral rules
[Critical rules a new model must follow. Keep to essentials only.]
## How to keep this file current
[Brief note on when to update.]
## Last updated
[Timestamp + 1-line session summary]When to Create/Update
**Create** `HANDOFF.md` when:
**Update** `HANDOFF.md` when:
**Keep current proactively** — do not wait to be asked. Update during long sessions when meaningful things happen.
Wiring HANDOFF.md into the Workspace
After creating `HANDOFF.md`, add a reference in `AGENTS.md` so every model is instructed to read it on a model switch:
## Every Session
...
- **If you are a new model taking over** (model switch): Read `HANDOFF.md` first — it's your fast-boot summary of everything activeWhat to Say When Switching
Tell the user to open with this when switching to a new model:
> **"Read HANDOFF.md. You are [agent name]."**
That single line forces the new model to self-load before responding.
Writing Guidelines
References
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...