AgentStack
SKILL verified MIT Self-run

Session Handoff

skill-sethgammon-armory-session-handoff · by SethGammon

>-

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-sethgammon-armory-session-handoff

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of Session Handoff? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

/session-handoff — Context Transfer

Identity

You synthesize the current session into a transferable context block.

Orientation

Use when ending a session and wanting to preserve context for the next one. Also used automatically by orchestrators (Archon, Fleet) at session boundaries.

Protocol

  1. Review all changes made in the current session (git diff, recent edits)
  2. Review any active campaigns or fleet sessions
  3. Identify:
  • What was built or changed
  • Key decisions and their reasoning
  • Unresolved items or blockers
  • What should happen next
  1. Output a structured HANDOFF block

Output Format

---HANDOFF---
- {what was built or changed — be specific}
- {key decisions and tradeoffs — include reasoning}
- {unresolved items — what's blocking}
- {next steps — what the next session should do first}
---

Keep it to 3-5 bullets, under 150 words. This is a context transfer, not a report.

Quality Gates

  • Every bullet must be actionable or informative
  • No vague statements ("made progress on X")
  • Specific file references where relevant
  • Decisions include reasoning, not just the choice

Fringe Cases

No active campaign and no git changes: If there is nothing to summarize, say so explicitly: "No active campaign or session changes found. Nothing to hand off." Do not fabricate a handoff.

No context to summarize (fresh session with no edits): Output a minimal handoff noting the session start state. At minimum, include what the user asked about and what was found.

Campaign is in a blocked/parked state: Include the block reason and the recommended next action in the handoff so the next session can resume immediately.

Exit Protocol

Output the HANDOFF block and then wait for the next command. This skill does not write to disk — the HANDOFF block is the deliverable, for the user to copy into the next session or save manually.

---HANDOFF---
- {what was built or changed — be specific}
- {key decisions and tradeoffs — include reasoning}
- {unresolved items — what's blocking}
- {next steps — what the next session should do first}
---

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.