obsidian-7-sync-strategies
Sub-skill of obsidian: 7. Sync Strategies (+1).
Best use case
obsidian-7-sync-strategies is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of obsidian: 7. Sync Strategies (+1).
Teams using obsidian-7-sync-strategies should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/7-sync-strategies/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How obsidian-7-sync-strategies Compares
| Feature / Agent | obsidian-7-sync-strategies | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of obsidian: 7. Sync Strategies (+1).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 7. Sync Strategies (+1) ## 7. Sync Strategies **Git-Based Sync:** ```bash #!/bin/bash # sync-vault.sh - Git-based vault sync VAULT_PATH="$HOME/Documents/ObsidianVault" cd "$VAULT_PATH" || exit 1 # Initialize if not a git repo if [ ! -d .git ]; then *See sub-skills for full details.* ## 8. Backup Strategies **Automated Backup Script:** ```bash #!/bin/bash # backup-vault.sh - Comprehensive vault backup VAULT_PATH="$HOME/Documents/ObsidianVault" BACKUP_DIR="$HOME/Backups/Obsidian" DATE=$(date +%Y-%m-%d_%H%M%S) BACKUP_NAME="obsidian-backup-$DATE" *See sub-skills for full details.*
Related Skills
worktree-branch-sync-hygiene
Class-level branch, worktree, dirty-main, stash, sync, and hook hygiene for workspace-hub style multi-repo work.
repo-sync
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
multi-repo-sync-diagnosis-repair
Diagnose and repair failed pulls across multi-repo ecosystems with stale locks, submodule conflicts, and untracked files
multi-repo-sync-diagnosis-and-repair
Systematic approach to diagnosing and repairing failures across a multi-repo workspace
workspace-hub-sync-root-churn-catchup
Catch up workspace-hub root changes that continue to appear during repo sync because live review/agent processes keep writing files after commits
workspace-hub-sync-concurrent-writer-blocks
Handle repository_sync cleanup when workspace-hub root is being mutated by concurrent Codex/Codex/Gemini sessions.
user-approved-plan-state-sync
Reconcile GitHub and local repo state when a plan has been user-approved, including direct approval messages that require creating the local marker and moving the issue to status:plan-approved.
repo-sync-deleted-remote-branch-and-unrelated-history-recovery
Recover multi-repo sync failures caused by deleted upstream branches, stale git index locks, and local branches with unrelated history to the remote default branch.
plan-rerun-review-state-sync
Keep iterative plan-review reruns truthful by syncing prompt files, canonical review artifacts, and the plan's own review-summary narrative after each adversarial wave.
github-sync
Multi-repository synchronization coordinator for version alignment, dependency sync, and cross-package integration. Use for package synchronization, version management, documentation alignment, and coordinated releases across multiple repositories.
git-sync-manager-5-safe-branch-operations
Sub-skill of git-sync-manager: 5. Safe Branch Operations.
git-sync-manager-3-repository-status-check
Sub-skill of git-sync-manager: 3. Repository Status Check (+1).