How do I install the Obsidian Github Backup skill?

Run npx skillmds@latest add steven65026502/obsidian-github-backup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Obsidian Github Backup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Obsidian Github Backup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Obsidian Github Backup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Obsidian Github Backup?

steven65026502 (@steven65026502) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Obsidian Github Backup by steven65026502

Name: Obsidian Github Backup
Author: steven65026502

Obsidian Github Backup

Back up a local Obsidian vault to a private GitHub repository with safety checks. Use when the user asks to upload, sync, commit, push, or back up Obsidian notes or a vault to GitHub, especially when the backup must stay private and avoid committing API keys, private keys, local REST credentials, or other secrets.

steven65026502 9cd038b 4 files · 9.3 KB Updated Sep 17, 2026

File contents

Obsidian GitHub Backup

Use this skill to back up an Obsidian vault to GitHub as a private repository.

Required Inputs

Vault path: obtain the actual path from the user; never guess a username or vault name.
GitHub repository: require owner/repository from the user.
Branch: default to main unless the existing repository uses another branch.
Required privacy: private.
Known sensitive file to exclude: .obsidian/plugins/obsidian-local-rest-api/data.json.

Workflow

Inspect the vault.
- Confirm the vault path exists.
- Check total file count and size.
- Check whether the vault already has .git/.
Protect secrets before staging.
- Ensure .gitignore excludes .obsidian/plugins/obsidian-local-rest-api/data.json.
- Do not remove the local file; just prevent it from being tracked.
- Scan staged contents for private-key patterns before commit.
Confirm GitHub privacy.
- Use Git Credential Manager when available.
- Create the backup repo if missing.
- If the repo exists but is public, switch it to private before pushing.
Commit and push.
- Use main.
- Commit only when there are changes.
- Use a precise commit message such as Back up Obsidian vault YYYY-MM-DD HH:mm.
Report clearly.
- Repo full name and visibility.
- Commit SHA or "no changes".
- Files tracked and excluded.
- Any warnings, especially files intentionally excluded.

Recommended Command

Run the bundled script with explicit vault and repository parameters:

$script = Join-Path $env:USERPROFILE ".agents\skills\obsidian-github-backup\scripts\backup_obsidian_to_github.ps1"
powershell -ExecutionPolicy Bypass -File $script `
  -VaultPath "<FULL_PATH_TO_VAULT>" `
  -RepositoryFullName "<OWNER>/<PRIVATE_REPOSITORY>"

Do not run the script while placeholders remain. Confirm both resolved values with the user first.

Policy Notes

Read references/default-policy.md if you need the exact include/exclude policy or need to explain why a file was excluded.

---name: obsidian-github-backupdescription: Back up a local Obsidian vault to a private GitHub repository with safety checks. Use when the user asks to upload, sync, commit, push, or back up Obsidian notes or a vault to GitHub, especially when the backup must stay private and avoid committing API keys, private keys, local REST credentials, or other secrets.---# Obsidian GitHub BackupUse this skill to back up an Obsidian vault to GitHub as a private repository.## Required Inputs- Vault path: obtain the actual path from the user; never guess a username or vault name.- GitHub repository: require `owner/repository` from the user.- Branch: default to `main` unless the existing repository uses another branch.- Required privacy: private.- Known sensitive file to exclude: `.obsidian/plugins/obsidian-local-rest-api/data.json`.## Workflow1. Inspect the vault. - Confirm the vault path exists. - Check total file count and size. - Check whether the vault already has `.git/`.2. Protect secrets before staging. - Ensure `.gitignore` excludes `.obsidian/plugins/obsidian-local-rest-api/data.json`. - Do not remove the local file; just prevent it from being tracked. - Scan staged contents for private-key patterns before commit.3. Confirm GitHub privacy. - Use Git Credential Manager when available. - Create the backup repo if missing. - If the repo exists but is public, switch it to private before pushing.4. Commit and push. - Use `main`. - Commit only when there are changes. - Use a precise commit message such as `Back up Obsidian vault YYYY-MM-DD HH:mm`.5. Report clearly. - Repo full name and visibility. - Commit SHA or "no changes". - Files tracked and excluded. - Any warnings, especially files intentionally excluded.## Recommended CommandRun the bundled script with explicit vault and repository parameters:```powershell$script = Join-Path $env:USERPROFILE ".agents\skills\obsidian-github-backup\scripts\backup_obsidian_to_github.ps1"powershell -ExecutionPolicy Bypass -File $script ` -VaultPath "<FULL_PATH_TO_VAULT>" ` -RepositoryFullName "<OWNER>/<PRIVATE_REPOSITORY>"```Do not run the script while placeholders remain. Confirm both resolved values with the user first.## Policy NotesRead `references/default-policy.md` if you need the exact include/exclude policy or need to explain why a file was excluded.

Frequently asked questions