obsidian-sync
Obsidian Sync
State file: ~/.openclaw/skill-state/obsidian-sync/state.yaml
Your agent's memory should be readable by you, not just by the agent.
When to Use
- On 10pm nightly cron wakeup
- When the user asks to sync notes to Obsidian
- After a major task completion worth archiving
Setup (First Run)
On first run, ask the user for their vault path and write it to state as vault_path. Do not proceed until this is set.
The Sync Process
Step 1: Read Agent Memory
More from archieindian/openclaw-superpowers
context-window-management
Prevents context overflow on long-running OpenClaw sessions. Use when approaching context limits.
28heartbeat-governor
Enforces per-skill execution budgets for scheduled cron skills — pauses runaway skills that exceed their token or wall-clock budget before they drain your monthly API allowance.
27using-superpowers
Bootstrap skill — teaches the agent how to find and invoke skills. Use when starting any new task or session.
23long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
22fact-check-before-trust
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
21persistent-memory-hygiene
Keeps OpenClaw's memory store clean, structured, and useful. Use at session end and during periodic maintenance.
20