SkillsHandoff

Context transfer

Long chats go bad. Starting over is worse.

Packs a whole conversation into one handoff block you paste into a fresh chat. Eight fixed sections, nothing important dropped, and two rules that stop the new chat drifting.

Works inClaudeChatGPTGemini

Free. No email required, nothing to download.

What it does

Eight sections, every time.

1. Objective

What you are ultimately trying to achieve, so the new chat knows what it is working towards before it reads anything else.

2. Current task

Exactly what you were working on when you stopped, separated from the wider goal so the two never get confused.

3. Decisions and constraints

Choices already made and why, approaches you rejected, plus the rules and preferences you have set. Recorded as settled, not as suggestions.

4. Progress

Split into completed, in progress and not started, so nothing gets done twice and nothing gets quietly dropped.

5. Critical context

Names, numbers, dates, URLs, products and file names, kept word for word. Uploaded files are listed here so you know what to re-attach.

6. Working material

The latest draft, prompt, plan or code, in full. This one is never summarised, because a summary of your draft is not your draft.

7. Open questions

Anything unresolved or waiting on a decision, including anything discussed but never confirmed.

8. Next actions

Where you left off, then the next steps in order, so the new chat starts working instead of asking what you want.

When to use it

  • The chat is getting long or slow. Answers get vaguer and earlier details get dropped. Hand off before it gets worse, not after.
  • You are switching tools. Started in ChatGPT and want to finish in Claude, or the other way round. The block works in both.
  • You are handing work to someone else. Drop the block into Slack or an email and a colleague, or their AI, is up to speed in one read.
  • You are stopping for the day. Save the block to a doc. Tomorrow you restart clean instead of scrolling back through two hundred messages.
  • The work is moving into a Project. You brainstormed in a loose chat and now it is real. Carry the context across instead of retyping it.
  • You are about to pivot. Lock in what is already decided before you branch off, so the new direction does not quietly undo the old one.

How to use it

  1. 01
    Install it, or just paste it

    Save it as SKILL.md inside a folder called context-transfer and upload the zipped folder, or skip all that and paste the text in as your last message. Same output either way.

  2. 02
    Trigger it

    Type "context transfer" at the end of the chat. In ChatGPT you can also mention the skill with an @.

  3. 03
    Check two sections

    Read Decisions and Next actions. If either one is wrong, correct it now. This is the thirty second step that saves you an hour later.

  4. 04
    Paste it into the new chat

    It comes back as one code block, so it is a single click. Re-upload anything listed under Critical context, then let it continue from Next actions.

The skill

Copy this.

Save it as SKILL.md and upload it to Claude or ChatGPT, or paste it straight into a chat as your last message. Both routes give the same result.

399 words
---
name: context-transfer
description: Turns the current conversation into a compact but lossless handoff block that can be pasted into a brand-new chat so work continues with nothing important missing. Use when the user says "context transfer", "handoff", "hand this over", "move this to a new chat", "this chat is getting long", or asks for a summary another AI can pick up from.
---

# Context Transfer

Turn the current conversation into one standalone handoff that a fresh AI instance can read and continue from correctly, without access to the original chat.

## Rules

- Compress the wording, never the facts. Cut filler, keep every detail that affects the work.
- Do not invent missing information. If something was never stated, write "Not stated".
- Do not re-open decisions that have already been made. Record them as settled.
- If something was discussed but never confirmed, label it "Unconfirmed".
- Keep names, numbers, dates, URLs, file names, product names and terminology exactly as written.
- Working material (drafts, prompts, code, plans, structures) goes in verbatim, latest version only. Never summarise it.
- List any files or images that were uploaded by name, and note they must be re-uploaded in the new chat.
- Prioritise what a fresh instance needs to continue correctly over conversation history.

## Output

Return one code block and nothing else. It must start with the heading CONTEXT TRANSFER and use the sections below in this order. Leave no section out; write "None" if a section is empty.

```
CONTEXT TRANSFER

Instruction for the new chat: Read this handoff in full. Treat Decisions and
constraints as settled. Re-uploaded files are listed under Critical context.
Confirm you understand in two lines, then continue from Next actions.

1. OBJECTIVE
What we are ultimately trying to achieve.

2. CURRENT TASK
Exactly what we are working on right now.

3. DECISIONS AND CONSTRAINTS
Choices made (with the reason where it matters), rejected approaches and why,
requirements, preferences, style rules.

4. PROGRESS
Completed:
In progress:
Not started:

5. CRITICAL CONTEXT
Names, numbers, dates, URLs, files, products, examples and terminology where
accuracy matters. Files to re-upload.

6. CURRENT WORKING MATERIAL
Latest version of any draft, prompt, plan, code or structure needed to
continue, in full.

7. OPEN QUESTIONS AND BLOCKERS
Anything unresolved or waiting on a decision.

8. NEXT ACTIONS
Where we left off, then the next logical steps in order.
```

What it will not do

  • It only hands over what the AI can still see. In very long chats the earliest messages may already be compressed or gone. Run it at natural checkpoints rather than once things are already falling apart.
  • Files do not travel. Uploads and images stay in the old chat. The block names them so you know exactly what to re-attach.
  • It is still written by an AI. Check any number, price or date that matters before you build on it.
  • Big drafts make big blocks. Working material is kept in full on purpose. If the chat holds a five thousand word draft, the handoff holds it too.

Common questions

  • What is a context transfer? One block of text that carries everything a fresh AI chat needs to continue your work: the objective, the current task, the decisions already made, progress, critical details, the latest draft, open questions and next actions. You paste it into the new chat and carry on.
  • Why does the new chat not drift? Two rules in the skill. The AI is not allowed to invent anything it does not know, so it writes "Not stated" rather than filling a gap with a guess that reads like a fact. And it is not allowed to re-open decisions you have already made, so they are recorded as settled and the new chat continues the work instead of relitigating it.
  • Does this work in both Claude and ChatGPT? Yes. Both read the same SKILL.md format, so the same file installs in either. Skills in ChatGPT are currently limited to Business, Enterprise, Edu and Healthcare workspaces, and on any other plan you paste the text in as a prompt instead.
  • Do I need a paid plan? Not for Claude. Skills work on Free, Pro and Max, though you have to switch on code execution and file creation under Settings, then Capabilities. In ChatGPT the Skills area is business plans only, and the paste version works on every plan, including Gemini.
  • Why did my skill upload fail? Almost always because the zip holds the loose SKILL.md rather than the folder. Zip the context-transfer folder itself, keep the folder name lowercase with hyphens, and make sure it matches the name line inside SKILL.md exactly.
  • Will it carry over my uploaded files? No. Files and images stay in the chat you uploaded them to. The handoff lists them by name under Critical context, so you know exactly what to re-upload on the other side.

Want this running without you?

A clean handoff is one small fix. We build the system that keeps your context in one place and does the work every week, then either hand it to your team or run it for you.

← All skills