Is handoff-close safe to install?

SaferSkills independently audited handoff-close (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/handoff-close/SKILL.md · 1 file

skills/handoff-close/SKILL.md2.2 KB · Markdown

name: handoff-close

description: >

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.

argument-hint: "[number or topic]"

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.

handoff-close— agent skill

Is handoff-close safe to install?

Handoff: Close

Step 1 — Resolve which handoff

Step 2 — Show what will be closed and confirm

Step 3 — Delete the file

Step 4 — Confirm

Audit the pieces. Scan the whole. Decide.