agentsclimarketplace

Handoff

Skill marsmike/agentic-toolkit/plugins/handoff/skills/handoff

Vault-first toolkit for Claude Code — curated plugins over an Obsidian-compatible knowledge vault, governed by an explicit contract, gated by evals, continuously delivered.

Install
npx -y skills add marsmike/agentic-toolkit --skill handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 10 days oldThe repository was created 10 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Save a portable handoff of current work to _handoff/ so another session, machine, or tool (Codex, Gemini) can continue without re-deriving context.

SKILL.md

2.3 KB, as published. Nobody here has run it

Handoff

Portable, tool-agnostic session continuity. A handoff is plain markdown written to _handoff/ inside the current repo (travels with the code to any machine or tool), with a one-line pointer appended to the vault's discovery index — best-effort, silently skipped when no vault is resolvable (see ../../README.md).

The deterministic mechanics live in ../../scripts/handoff.py. Your job is the narrative — the part only conversation context can produce. Write forward: for what the next window needs to act, not a log of finished work.

Quick start

Save a handoff of what we're doing so I can continue later

  1. Pick a stream tag — short kebab-case name for this line of work (e.g. auth-fix, html-export). Reuse the same tag across sessions on the same effort so they chain (seq 1 → 2 → 3). If the user passed one via $ARGUMENTS, use it.
  2. Write the narrative to _handoff/.draft.md using the section template in references/template.md. Fill every section from the conversation. The two highest-value sections are Tried & Ruled Out (so the next session never re-explores dead ends) and Next Step (the exact action to take, with file:line pointers). Keep it tight — decisions and direction, not narration.
  3. Assemble & write by running the script (it adds frontmatter, git state, the chain link, and the vault index line): 
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/handoff.py" save \
  --stream <tag> --title "<one-line title>" \
  --body-file _handoff/.draft.md
  4. Report the saved path and vault-index line back to the user, and surface the script's own Suggested: line — it already reads the profile's default_visibility (commit for team/cross-machine continuity, gitignore for private single-machine use) so you don't have to guess.

Full procedure detail — listing existing handoffs, cross-tool (Codex/Gemini) handoff, the auto-snapshot safety net, chain integrity, and the storage model — lives in references/workflow.md.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.