Handoff
Use when a session is ending or work is passing to a fresh session or another agent — so the next one resumes without re-deriving goal, state, decisions, and the next step. Skip for a finished, self-contained task that needs no continuation.
Install
$ agentstack add skill-njoyimpeguy-augments-handoff ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-njoyimpeguy-augments-handoff) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Handoff
Write down what the next session needs to continue, so it doesn't reconstruct it from scratch. A good handoff is resumable: someone reads it and knows exactly where to pick up.
When to use
- A conversation is ending mid-work, or work is passing to a fresh session or a different agent.
- Skip when the task is finished and self-contained — there's nothing to resume.
What to capture
Write it to a scratch location outside the workspace (the OS temp directory), so it doesn't pollute the repo. Include:
- The goal — what this work is trying to achieve, in a line or two.
- State — what's done, what's in flight, the current branch, and any uncommitted changes.
- Decisions — the choices made and why, so they aren't relitigated.
- Gotchas — traps discovered, with file and line references.
- The next step — the single concrete thing to do next.
- Suggested skills — which skills the next session should reach for. Put this in the document, not in passing chat.
Rules
- Reference, don't duplicate. Point to existing artifacts (specs, plans, ADRs, issues, commits) by path or URL — don't copy their content in.
- Redact secrets. No keys, tokens, passwords, or personal data in the handoff.
- A handoff is a one-shot transfer of current state — not a durable project-lessons store.
Common mistakes
- A summary of the conversation instead of the state to resume from.
- Duplicating a plan or spec that already exists — link it.
- Omitting the one concrete next step, leaving the next session to guess.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: NjoyimPeguy
- Source: NjoyimPeguy/augments
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.