Handoff
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is purpose-aligned for creating and updating local Obsidian handoff notes, with confirmation before writes, though users should be careful about what gets stored in the shared vault.
This skill appears safe to install if you want agents to manage handoff notes in the shared Obsidian vault. Before approving writes, check the destination path and content, especially for permanent knowledge updates or work logs that may be reused later.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the user confirms, the agent may create or modify local Obsidian vault files.
The skill is intended to create or edit vault files, but it explicitly requires path disclosure and user confirmation before file mutation.
Before any write or edit, you MUST: 1) state the resolved absolute path(s) you intend to write, and 2) ask the user to confirm.
Review the exact path and proposed content before confirming any write or edit.
Project details, work logs, or incorrect assumptions could persist in shared notes and influence future handoffs or knowledge use.
The skill stores handoff and knowledge material in a persistent shared vault, which may later be read or relied on by users or agents.
Root: `$HOME/.openclaw/shared/` (Obsidian vault) ... Permanent knowledge: `$HOME/.openclaw/shared/knowledge/<project>/...`
Avoid storing secrets or sensitive command output, and review permanent knowledge changes carefully before applying them.