Individual skill

session-handoff

Write a handoff summary so another agent or person (or a fresh session) can pick up the work with full context. Use when ending a work session, hitting a context limit, switching agents, or pausing a task mid-flight. Produces a structured handoff: what the goal is, what's done, the current state, what's next, and the gotchas — so no context is lost across the boundary.

plugins/pm-tokens/skills/session-handoff/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Session Handoff Skill

Work gets dropped at boundaries — a context window fills, a session ends, a task passes to someone else — and
the next person (or agent) re-derives everything from scratch. This skill writes a tight **handoff** that
carries the state across that boundary: the goal, what's done, where things stand, the exact next step, and
the landmines. Optimised to be the first thing a fresh session reads.

## Required Inputs

Ask for these only if they aren't already provided (or infer from the session so far):

- **The objective** — what we're ultimately trying to achieve.
- **Progress** — what's been done and decided so far.
- **Current state** — what's in-flight right now, what's working/broken, where files/branches are.
Back to top