Handoff
Compacts the current conversation into a handoff document so a fresh agent session can pick up the work
Curated by Skill Harbor — a small, sharp skill that writes a handoff document summarising the current conversation so a fresh agent can continue the work without re-deriving everything. Best moment to use it: you are in the middle of a long conversation and want to start fresh in a new session without re-deriving everything. It saves the document to the OS temp directory (not the workspace), includes a "suggested skills" section naming which skills the next agent should call, references existing artifacts by path or URL instead of duplicating them, and redacts sensitive information like API keys, passwords and personal data. If you pass arguments, it treats them as what the next session will focus on and tailors the document. By @mattpocock, listed here with credit to its creator. Honest caveats: the handoff is only as good as the conversation it summarises — vague sessions produce vague handoffs; it writes outside your project folder by design (OS temp dir), so know where to look. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Handoff, by Matt Pocock, compacts your current conversation into a handoff document so a fresh agent session can pick up the work without re-deriving everything. The document is saved to your OS temp directory, includes a suggested-skills section naming what the next agent should call, references your existing artifacts by path or URL instead of duplicating them, and redacts sensitive information like API keys, passwords and personal data.
At a glance
| What it is | A small skill that writes a structured summary of a working session, addressed to the next agent session. |
|---|---|
| Who it's for | Anyone whose work spans multiple agent sessions and who is tired of re-explaining context every time a fresh session starts. |
| What you give it | The conversation you want to hand off. Pass arguments and it treats them as what the next session will focus on, and tailors the document to that. |
| What you get | A handoff document in the OS temp directory: the state of the work, a suggested-skills section for the next agent, and pointers to your artifacts — with sensitive information redacted. |
| Works with | Agent sessions that run skills; install it from this listing with the copy-paste install prompt in the Install section. The listing's own caveat: the handoff is only as good as the conversation it summarizes. |
| Cost | Free — this listing is free. |
| Time | Moments to run at the end of a session; the saving is the context a fresh session does not have to rebuild from scratch. |
Example — ending today, resuming tomorrow
An example of how you might use it, based on what the skill documents:
- You are deep in a project and the session is getting long, so you invoke Handoff and tell it the next session will focus on the tests.
- It writes the handoff to the temp directory: where the work stands, the suggested skills to call next, and links to the files involved — credentials and personal data redacted.
- Tomorrow, a fresh session reads the document and continues from there, instead of asking you to recap everything.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 49dd158Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Muse account with skill installation enabled Install "Handoff" for me. Compacts the current conversation into a handoff document so a fresh agent session can pick up the work Repository: https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/skills/productivity/handoff/SKILL.md Pinned version: install the code at commit 49dd158d1076134a641b33efb035946536778336 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-handoff". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 49dd158 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.