How do I install the Handoff Close skill?

Run npx skillmds@latest add danielsitek/handoff-close in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Handoff Close safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Handoff Close?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Handoff Close free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Handoff Close?

danielsitek (@danielsitek) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Handoff Close by danielsitek — Agent Skill

Name: Handoff Close
Author: danielsitek

Handoff Close

Close a resolved handoff by number and delete its file from .handoffs/. Use this skill whenever the user is done with a parked task and wants to clear it — phrases like "close handoff 2", "handoff 3 is done", "remove that handoff", "delete handoff-0001", "ten handoff je hotový". Trigger when the user signals a handoff is finished and should be removed. This skill deletes a file, so it confirms before deleting unless the user gave an unambiguous numbered instruction.

danielsitek 2b06f2d 2.1 KB Updated Sep 17, 2026

File contents

Handoff: Close

When a parked task is resolved, its handoff file is no longer needed. Closing a handoff means deleting .handoffs/handoff-NNNN.md.

Because this permanently removes a file, always confirm before deleting.

Step 1 — Resolve which handoff

If .handoffs/ does not exist or is empty, tell the user there are no saved handoffs to close and stop.
If the user gave a number, target .handoffs/handoff-NNNN.md (zero-pad it).
If they referred to a topic instead, match it against the title and <handoff-summary> of the files; if ambiguous, ask which one.
If the specific file does not exist, say so and list the handoffs that do exist.

Step 2 — Show what will be closed and confirm

Read the file and show the user the number, title, and summary of the handoff about to be deleted, so they can confirm it is the right one. Ask for explicit confirmation before deleting — for example:

Handoff 0002 — "Migrate config to TypeScript". Closing this will delete .handoffs/handoff-0002.md permanently. Go ahead?

If the user already gave a clear, unambiguous instruction to delete a specific numbered handoff, you may treat that as confirmation and proceed — but still show what is being removed.

Step 3 — Delete the file

Remove the file:

rm .handoffs/handoff-NNNN.md

(On Windows: Remove-Item .handoffs\handoff-NNNN.md)

(In some environments deleting a file may prompt for permission — that is expected; let the user approve it.)

Step 4 — Confirm

Tell the user the handoff was closed and deleted. Optionally mention how many handoffs remain, or suggest handoff-list to see the rest.

---name: handoff-closedescription: Close a resolved handoff by number and delete its file from .handoffs/. Use this skill whenever the user is done with a parked task and wants to clear it — phrases like "close handoff 2", "handoff 3 is done", "remove that handoff", "delete handoff-0001", "ten handoff je hotový". Trigger when the user signals a handoff is finished and should be removed. This skill deletes a file, so it confirms before deleting unless the user gave an unambiguous numbered instruction.---# Handoff: CloseWhen a parked task is resolved, its handoff file is no longer needed. Closing ahandoff means deleting `.handoffs/handoff-NNNN.md`.Because this permanently removes a file, always confirm before deleting.## Step 1 — Resolve which handoff- If `.handoffs/` does not exist or is empty, tell the user there are no saved handoffs to close and stop.- If the user gave a number, target `.handoffs/handoff-NNNN.md` (zero-pad it).- If they referred to a topic instead, match it against the `title` and `<handoff-summary>` of the files; if ambiguous, ask which one.- If the specific file does not exist, say so and list the handoffs that do exist.## Step 2 — Show what will be closed and confirmRead the file and show the user the number, title, and summary of the handoffabout to be deleted, so they can confirm it is the right one. Ask for explicitconfirmation before deleting — for example:> Handoff `0002` — "Migrate config to TypeScript". Closing this will delete> `.handoffs/handoff-0002.md` permanently. Go ahead?If the user already gave a clear, unambiguous instruction to delete a specificnumbered handoff, you may treat that as confirmation and proceed — but stillshow what is being removed.## Step 3 — Delete the fileRemove the file:```bashrm .handoffs/handoff-NNNN.md```(On Windows: `Remove-Item .handoffs\handoff-NNNN.md`)(In some environments deleting a file may prompt for permission — that isexpected; let the user approve it.)## Step 4 — ConfirmTell the user the handoff was closed and deleted. Optionally mention how manyhandoffs remain, or suggest `handoff-list` to see the rest.

Frequently asked questions