Cs Handoff Setup

First-run setup for the handoff skill. Walks 5 questions (save location, retention, redaction strictness, git context, recommender scope) and writes the config. Run any time to reconfigure.

Published by @Alireza Rezvani·from alirezarezvani/claude-skills·0 agent reads / 30d·0 saves·

/cs:handoff-setup

Configure the handoff skill. Walks 5 questions (plus 1-2 optional) and writes the config. Re-run any time.

Invocation

/cs:handoff-setup                 # configure global defaults
/cs:handoff-setup --project       # set project-specific overrides

Questions

  1. Save location — OS temp / home folder / hidden home folder / per-project / custom. No pre-selected default — explicit choice required on first run.
  2. Retention window — 7 / 30 days / forever / manual.
  3. Redaction strictness — strict / warn / off.
  4. Git context — auto-include branch + last commit + dirty file count? yes/no.
  5. Skill recommendation scope — all repo / current domain only / off.
  6. Filename style (only if save location ≠ temp) — date_slug / timestamp / mktemp.

Behaviour

  • Global config at ~/.config/handoff/config.json.
  • Project override at <repo>/.handoff/config.json (with --project). Missing keys fall back to global.
  • For save_location.mode = project, setup offers to append .handoff/ to .gitignore.
  • Idempotent. Re-running pre-fills current values.

Reset to defaults

Delete the config and rerun:

rm ~/.config/handoff/config.json
rm ~/.config/handoff/.setup-declined 2>/dev/null

Run

python3 ${CLAUDE_PLUGIN_ROOT}/skills/handoff/scripts/setup.py

For project-scoped overrides:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/handoff/scripts/setup.py --reconfigure --project

Bundled with this artifact

2 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Incident Commander

Comprehensive incident response framework from detection through resolution and post-incident review. Battle-tested SRE/DevOps practices: severity classification, timeline reconstruction, structured post-incident analysis. Use when declaring an incident, coordinating multi-team response during an outage, leading a post-mortem, or setting up on-call practices for a new service.

software-engineering+2
6
SKILL0

Archive

Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says "archive this". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.

software-engineering+2
0
SKILL0

Ms Teams Apps

Microsoft Teams bots and AI agents - Claude/OpenAI, Adaptive Cards, Graph API

software-engineering+2
0