Obsidian Openclaw Sync
ReviewAudited by ClawScan on May 1, 2026.
Overview
This skill’s artifacts coherently describe an iCloud/Obsidian sync helper, but it can persistently change shared OpenClaw configuration across devices, so users should review what vault they sync before using it.
This appears to be a legitimate sync helper for OpenClaw and Obsidian on iCloud. Before installing or running setup, verify the selected iCloud vault, review its skills and workspace files, and keep a backup of local OpenClaw configuration—especially before using --overwrite or --no-confirm.
Findings (4)
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 used on the wrong vault or without review, local OpenClaw configuration may be replaced by iCloud-backed configuration.
The skill documents user-selected options that can replace local agent configuration and bypass confirmation prompts.
`--overwrite` ... `Overwrite local openclaw.json with symlink to iCloud version`; `--no-confirm` ... `Skip confirmation prompt (auto-confirm)`
Use the interactive setup first, confirm the selected vault, and back up openclaw.json before using --overwrite or --no-confirm.
Unreviewed or stale content in the iCloud vault could influence future agent behavior across sessions.
The synced paths include persistent skills, workspaces, and OpenClaw configuration that may be reused by agents in later tasks.
`skills/` | `./skills/`; `workspace-*/` | `./workspace-*/`; `.openclaw/*.json` | `./.openclaw/*.json`
Inspect the iCloud vault’s skills, workspace folders, and .openclaw JSON files before syncing them into local agent configuration.
A mistaken overwrite or bad configuration in one synced vault can spread to other devices using the same iCloud-backed setup.
The skill intentionally propagates OpenClaw configuration changes through iCloud to multiple devices.
**All devices**: Changes sync via iCloud Drive automatically
Test with one device first, keep backups, and avoid syncing untrusted vault content across all devices.
Users have less external provenance information and may need to manually verify that the environment matches the documented requirements.
The registry metadata provides limited provenance and does not declare the macOS/Python expectations that the skill documentation relies on.
Source: unknown; Homepage: none; OS restriction: none; Required binaries ... none
Install only if you trust the publisher, and confirm you are on macOS with Python available before invoking the skill.