Individual skill

handoff

0upvotes

Compact the current conversation into a handoff document for a fresh agent.

skills/handoff/SKILL.md

Read pinned source

Source commit ced546848ec8eea8541e77b7aa041207b607462e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 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): 20
Repository last updated: Oct 26, 2026
License: MIT

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

agent-skills Repository topic
skills Repository topic
cursor Repository topic
antigravity Repository topic
claude-code Repository topic
agents Repository topic
codex Repository topic
engineering Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 992 bytes

Read excerpt


Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to `$TMPDIR`, else `/tmp` (`%TEMP%` on Windows) - not the current workspace - and print the absolute path.

Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.

Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

Redact any sensitive information, such as API keys, passwords, or personally identifiable information.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

Next: in the fresh session, `/hb:triage` with the handoff path, or the first suggested command from the doc.