handoff
Generate a handoff summary and copy to clipboard for new session
What this skill does
Generate a concise handoff summary of our conversation that I can use to continue in a new Claude Code session.
Use this exact format:
```
## What we're working on
- [Primary task/topic]
- [Secondary items if applicable]
## Current state
- [Where we left off]
- [Any pending questions or decisions]
## Key decisions made
- [Important choices/conclusions from this conversation]
## Recent changes
- [Files modified, if any]
- [Commands run or actions taken]
## Important context
- [Facts, preferences, or constraints I mentioned]
- [Technical details that matter for continuing]
## Next steps
- [Immediate next action]
- [Follow-up tasks]
```
Requirements:
- Be concise but complete - capture what's needed to continue without re-explaining
- Focus on actionable state, not conversation history
- Include file paths and technical specifics where relevant
- Skip sections that don't apply (e.g., "Recent changes" if no files were modified)
After generating the summary, copy it to clipboard using this bash command:
```bash
# Detect environment and copy accordingly
if command -v clip.exe &> /dev/null; then
# WSL with Windows clipboard
cat <<'HANDOFF_EOF' | clip.exe
[INSERT THE GENERATED HANDOFF SUMMARY HERE]
HANDOFF_EOF
echo "✅ Handoff copied to clipboard (WSL/Windows)"
elif command -v xclip &> /dev/null; then
# Linux with xclip
cat <<'HANDOFF_EOF' | xclip -selection clipboard -i &>/dev/null &
[INSERT THE GENERATED HANDOFF SUMMARY HERE]
HANDOFF_EOF
sleep 0.2
echo "✅ Handoff copied to clipboard (xclip)"
elif command -v xsel &> /dev/null; then
# Linux with xsel
cat <<'HANDOFF_EOF' | xsel --clipboard --input
[INSERT THE GENERATED HANDOFF SUMMARY HERE]
HANDOFF_EOF
echo "✅ Handoff copied to clipboard (xsel)"
elif command -v wl-copy &> /dev/null; then
# Wayland
cat <<'HANDOFF_EOF' | wl-copy
[INSERT THE GENERATED HANDOFF SUMMARY HERE]
HANDOFF_EOF
echo "✅ Handoff copied to clipboard (Wayland)"
elif command -v termux-clipboard-set &> /dev/null; then
# Termux
cat <<'HANDOFF_EOF' | termux-clipboard-set
[INSERT THE GENERATED HANDOFF SUMMARY HERE]
HANDOFF_EOF
echo "✅ Handoff copied to clipboard (Termux)"
else
echo "⚠️ No clipboard tool found. Install xclip, xsel, or wl-clipboard"
echo ""
echo "Manual copy - here's the handoff:"
echo "================================"
cat <<'HANDOFF_EOF'
[INSERT THE GENERATED HANDOFF SUMMARY HERE]
HANDOFF_EOF
fi
```
Then display:
```
✅ Handoff summary copied to clipboard!
To continue in a new session:
1. Start new Claude Code session: claude
2. Paste the handoff (Ctrl+V or Ctrl+Shift+V)
3. Add your next question/task after the handoff
💡 The handoff provides context so Claude understands where you left off.
```
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.