Run any Skill in Manus with one click

handoff

Stars2

Forks0

UpdatedJune 24, 2026 at 14:07

Generate a concise session-handoff summary — TL;DR, what changed, decisions taken, open items, and context for the next session — and optionally save it to the Obsidian vault _wip/ inbox via the capture skill. Use at the end of a working session, when switching context, or when the user says "handoff", "hand this off", "wrap up", "session summary", or "/handoff". Never include raw credentials or PII; use surrogates.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hankthebldr

hankthebldr/dot-files

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Office Clerks, GeneralOffice and Administrative Support Occupations·SOC 43-9061

SKILL.md

readonly

name

handoff

description

Session Handoff

Compose a concise handoff for the current session (or a specific topic if one is given).

Output structure

## TL;DR
<2-3 sentences. What was done, what's next, what's blocking>

## What changed
- <commits, configs, infra deltas>

## Decisions taken
- <one-liner per decision, with link/ref to a spec/ADR if applicable>

## Findings (if any)
<reference the report-writeup skill format if recon was involved>

## Open items / followups
- [ ] <task> — owner — due

## Context for next session
<short paragraph: what state the work is in, what to read first, what to run>

Storage

Default: print to chat for review.
If the operator confirms: save through the obsidian-vault-capture skill (capture_note.py in Claude Code, or vault_create_note in chat/Cowork) into _wip/ as YYYY-MM-DD-handoff-<slug>.md with --type reference --tags "handoff, <project>" and an explicit --area so the router can classify it (a handoff with no area returns "no routing signal" and stalls in _wip). Use the handoff tag plus --area matching the work's domain (lab, panw-gtm, the relevant Cortex area, etc.). _wip/ is the vault's inbox; the router files it on the next vault_route_note(apply=True) / oroute run. (Legacy /handoff targeted 00-Inbox/handoffs/; _wip/ is now the canonical inbox.) type: capture is retired — the type vocabulary is working-note | research | reference | meeting | demo | discovery; use reference for a handoff.

Rules

Never overwrite an existing handoff — capture_note.py auto-suffixes collisions.
Never include raw credentials, API keys, or full PII. Use surrogates (engagement IDs, role labels).
If the session was OPSEC-sensitive (safeclaude route), add a one-line note: "Generated via OPSEC route. Surrogate values used."
This is session-level capture (a higher bar than per-run sync-log.md). It does not write project binding anchors — that is owned by docsync / the vault-os tools.

More from this repository

same repository

name

hankthebldr/dot-files

Use when … (one-line trigger: name the task, its inputs, and the situation it applies to). This sentence is what the model reads to decide whether to load the skill.

2026-06-242

docsync

hankthebldr/dot-files

Project-aware sync between a GitHub repo, its Things 3 project, and its Obsidian vault subdirectory. The repo NAME is the common key across all three surfaces. Use whenever an agent needs to create Things 3 todos tied to a repo, onboard a repo, or mirror a repo's key markdown into the vault. Replaces ad-hoc add_todo calls that silently land in the Inbox. Trigger on "docsync", "sync this repo to Things", "create a todo for {repo}", sprint planning that emits tasks, or any repo-scoped task capture.

2026-06-242

enrich-this-note

hankthebldr/dot-files

Analyze an Obsidian vault note and suggest enrichment — improved/missing frontmatter, 3-5 wikilinks to related vault notes, the right MOC to file it under, and a 1-sentence MOC summary. Use when the user asks to "enrich this note", wants frontmatter/tag/link/MOC suggestions for a note, or is triaging a _wip/ note. Suggests only; never overwrites frontmatter without confirmation.

2026-06-242

obsidian-vault-capture

hankthebldr/dot-files

Capture research findings, slash-command output, decisions, or other substantive session output as a structured Obsidian note in Henry's vault. Use this skill automatically whenever a session produces output with lasting reference value — research conclusions, comparison/evaluation results, command output worth keeping, architecture decisions, or notable findings — even if the user does not explicitly say "save this to my vault." Trigger on phrases like "capture this," "save to my vault," "note this," "vault this," and as the default RECORD/REFLECT step in autonomous loops. This is the canonical way to write vault notes; do not hand-roll frontmatter or write notes ad hoc when this skill applies.

2026-06-242

project-init

hankthebldr/dot-files

Onboard a GitHub repo as a vault dev-project — resolve (or create, with confirmation) its Things 3 project, then scaffold Github-Projects/<repo>/ with the _MOC <repo>.md binding anchor via the vault-os MCP tools. Use when starting work on a new repo, or when the user says "onboard <repo>", "project-init <repo>", "set up docsync for <repo>", or before the first /sync-docs on a repo. One-time per repo; afterward docsync and /sync-docs take the deterministic binding path automatically.

2026-06-242

simple

hankthebldr/dot-files

Invoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making.

2026-06-042

name

handoff

description

Session Handoff

Compose a concise handoff for the current session (or a specific topic if one is given).

Output structure

## TL;DR
<2-3 sentences. What was done, what's next, what's blocking>

## What changed
- <commits, configs, infra deltas>

## Decisions taken
- <one-liner per decision, with link/ref to a spec/ADR if applicable>

## Findings (if any)
<reference the report-writeup skill format if recon was involved>

## Open items / followups
- [ ] <task> — owner — due

## Context for next session
<short paragraph: what state the work is in, what to read first, what to run>

Storage

Default: print to chat for review.
If the operator confirms: save through the obsidian-vault-capture skill (capture_note.py in Claude Code, or vault_create_note in chat/Cowork) into _wip/ as YYYY-MM-DD-handoff-<slug>.md with --type reference --tags "handoff, <project>" and an explicit --area so the router can classify it (a handoff with no area returns "no routing signal" and stalls in _wip). Use the handoff tag plus --area matching the work's domain (lab, panw-gtm, the relevant Cortex area, etc.). _wip/ is the vault's inbox; the router files it on the next vault_route_note(apply=True) / oroute run. (Legacy /handoff targeted 00-Inbox/handoffs/; _wip/ is now the canonical inbox.) type: capture is retired — the type vocabulary is working-note | research | reference | meeting | demo | discovery; use reference for a handoff.

Rules

Never overwrite an existing handoff — capture_note.py auto-suffixes collisions.
Never include raw credentials, API keys, or full PII. Use surrogates (engagement IDs, role labels).
If the session was OPSEC-sensitive (safeclaude route), add a one-line note: "Generated via OPSEC route. Surrogate values used."
This is session-level capture (a higher bar than per-run sync-log.md). It does not write project binding anchors — that is owned by docsync / the vault-os tools.