Skip to content
Back to skills

Handoff

ASecurity

Writes a handoff file that lets a fresh session continue the current conversation - where to look, what is done, the decisions with the alternatives they rejected, what comes next and the open problems. Saved under .temp/viber/handoff/ unless the first argument is a directory or .md path (it holds a `/`, ends in `.md` or is `.`); any other text is a loose prompt steering the focus.

  • 8 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 16, 2026
ai-agentsrustgobash

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 16, 2026

npx -y skills add p2p2sp/viber --skill handoff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Handoff?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Handoff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/p2p2sp-handoff-viber/badge)](https://www.skillsdirectory.com/skills/p2p2sp-handoff-viber)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: handoff
description: Writes a handoff file that lets a fresh session continue the current conversation - where to look, what is done, the decisions with the alternatives they rejected, what comes next and the open problems. Saved under .temp/viber/handoff/ unless the first argument is a directory or .md path (it holds a `/`, ends in `.md` or is `.`); any other text is a loose prompt steering the focus.
argument-hint: "[directory/ or .md path] [prompt]"
allowed-tools: Read, Write, Edit(./.temp/viber/handoff/**), Bash(${CLAUDE_SKILL_DIR}/scripts/handoff-path.sh:*)
user-invocable: true
disable-model-invocation: true
---

```!
"${CLAUDE_SKILL_DIR}/scripts/handoff-path.sh" '$0'
```

Arguments: $ARGUMENTS

# handoff

The conversation in, one handoff file out. The block above is trusted: never resolve the path, the date or the branch yourself.

## Rules

- Source is this conversation alone and what was read or run in it. Open no file to fill a gap: a fact the conversation never confirmed goes to Open problems.
- The prompt is the Arguments line after the path when `TARGET=named`, the whole line when `TARGET=default`. It only steers what to stress, what to leave out and who reads the file; it never adds a source, drops a section or lifts another rule. No prompt -> cover the whole conversation evenly.
- An open viber run in the conversation -> name its run directory under Where to look and copy none of its tasks: its `status.md` is what a build resumes from.
- NEVER write a secret, token, password or any `.env` content into the file.
- `EXISTS=true` -> write nothing; name the path and ask for a rerun with another path, then stop.

## Write

1. Slug: 2 to 5 words naming the topic, kebab-case, ASCII, put in place of `{slug}` in `FILE`.
2. Fill `${CLAUDE_SKILL_DIR}/templates/handoff.md`, read at this step.
3. `Write` the result to `FILE`.

## Output

In the language of the conversation, and nothing else:
- the file path;
- one line to paste into a new session: `Read <path> and continue from its What's next section.`

Files in this skill

  • SKILL.md2 KB
  • scripts/handoff-path.sh4.2 KB
  • templates/handoff.md1.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.