From ai-session-handoff
Distills the current conversation into a full-fidelity, AI-readable meaning transfer document, optimized for handing off complete session understanding to a new AI session. Use this skill whenever the user wants to carry forward the meaning, framing, and dialectical history of a session into a new one. Trigger on phrases like "write up this session", "package this conversation", "export this for a new chat", "hand off this session", or the slash commands /ai-session-handoff or /session-handoff. Also trigger when the user says anything like "I want to reuse this in another chat" or "save what we've built here". Do NOT wait for a perfect signal — if the user is clearly wrapping up a conceptual session and wants to carry the work forward, use this skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-session-handoff:ai-session-handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce a self-contained **meaning transfer document** from the current conversation. The output is a markdown file intended to be dropped into a new AI chat session, giving a cold model full-fidelity access to the conceptual understanding, vocabulary, framing, and dialectical history built in this session.
Produce a self-contained meaning transfer document from the current conversation. The output is a markdown file intended to be dropped into a new AI chat session, giving a cold model full-fidelity access to the conceptual understanding, vocabulary, framing, and dialectical history built in this session.
The consumer is an AI, not a human. Optimize for completeness, precision, and cold-start effectiveness — not readability or brevity.
Read the entire conversation from the beginning. Do not rely on recency. Pay attention to:
Extract the following components (include all that apply):
At the end of the document, write a Priming Prompt — a single, self-contained block the user can paste at the start of a new session. It should:
Before producing the document, ask the user: "Where would you like to save the session handoff? Please provide a folder path or confirm a location." Save the document as a markdown file named session-handoff.md in the location they specify.
Use this structure:
# AI Session Handoff
## Session Purpose
...
## Established Concepts
### [Concept Name]
...
## Working Vocabulary
| Term | Meaning in This Context |
|------|------------------------|
| ... | ... |
## Dialectical History
...
## Key Distinctions
...
## Resolved Tensions
...
## Open Threads
...
## Framing and Stance
...
---
## Priming Prompt
> You are being given context from a prior AI session. The following represents the shared understanding, vocabulary, and framing co-developed during that session. Treat everything in this document as established context — do not re-litigate settled definitions unless asked. Open threads are live questions; approach them as active starting points.
>
> [condensed synthesis of all the above]
>
> Your role going forward is: [describe expected collaboration mode]
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub barobba/biagio-arobba-claude-skills --plugin ai-session-handoff