Obsidian GitHub Sync

This skill appears to do what it says (auto-commit, pull --rebase, push, and signal conflicts), but review and test before deploying. Concrete precautions: - Inspect the two scripts yourself. They run git init / git remote add and will modify the vault directory and .git metadata; run them first on a throwaway test copy of your vault. - The registry metadata does not declare required env vars; set and verify these before running: OBSIDIAN_VAULT_DIR and GITHUB_REMOTE_URL. Ensure the remote URL/branch is correct (script hardcodes 'origin master'). - The script relies on your Git/SSH credentials (it does not prompt for or store tokens). Ensure your SSH keys are configured and that you understand whether the remote uses 'main' vs 'master'. - Backup your vault before enabling automated cron/systemd runs. Automated commits + rebase can rewrite history or cause surprises if misconfigured. - Consider changing log/flag file locations and permissions if multiple users share the system; /tmp is world-readable on many systems and will contain repository path/remote in the flag file. - If you want the skill in an agent context, require that the agent only run it with an explicit configured OBSIDIAN_VAULT_DIR (avoid letting the skill infer paths) and avoid granting broad filesystem access. If you want, I can point out exact lines in the scripts to modify (branch name, logging path, preventing automatic git init/remote add) and produce a safer variant you can test.