From obsidian-pack
Implement vault data backup, sync, and recovery strategies. Use when building backup features, implementing data export, or handling vault synchronization in your plugin. Trigger with phrases like "obsidian backup", "obsidian sync", "obsidian data export", "vault backup strategy".
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-pack:obsidian-data-handlingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implement robust data handling patterns for vault backup, export, sync, and recovery in Obsidian plugins.
Implement robust data handling patterns for vault backup, export, sync, and recovery in Obsidian plugins.
For full implementation details and code examples, load:
references/implementation-guide.md
| Issue | Cause | Solution |
|---|---|---|
| Export fails | Large vault | Use streaming export |
| Import conflicts | Existing files | Provide overwrite option |
| Backup corruption | Interrupted write | Verify with checksum |
| Sync conflicts | Concurrent edits | Implement conflict resolution |
For team access patterns, see obsidian-enterprise-rbac.
Basic usage: Apply obsidian data handling to a standard project setup with default configuration options.
Advanced scenario: Customize obsidian data handling for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin obsidian-packGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
4plugins reuse this skill
First indexed Jul 11, 2026