agentsclimarketplace

Handoff close

Skill danielsitek/skills/skills/handoff-close

My personal directory of skills

Install
npx -y skills add danielsitek/skills --skill handoff-close

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.2 KB, 418 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most agent orchestration skills give in 418 tokens

Counted across 742 of the 995 authors here whose files we hold, read 2026-08-07

  • reference existing artifacts by path or URLin 53 of 742, across 25 files
  • run the full test suite after integrating changesin 51 of 742, across 19 files
  • dispatch one agent per independent problem domainin 50 of 742, across 17 files
  • verify fixes do not conflictin 45 of 742, across 13 files
  • include a suggested skills section in the documentin 45 of 742, across 17 files
  • redact sensitive informationin 41 of 742, across 11 files
  • save to the temporary directory of the operating systemin 39 of 742, across 10 files
  • tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
  • spot check agent changes for systematic errorsin 34 of 742, across 7 files
  • write a handoff document summarising the current conversationin 31 of 742, across 6 files
  • Assign each agent a specific scopein 23 of 742, across 8 files
  • provide specific scope and clear goalin 23 of 742, across 5 files

Said here and by no other author read

  • confirm before deleting
  • stop if the handoffs directory is empty
  • target the file by zero-padded number
  • match ambiguous topic references against titles and summaries
  • list existing handoffs if the target file is missing
  • show the number, title, and summary before deleting

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.