Skip to content
Back to skills

Sync Upstream Obsidianos

ASecurity

Pull structural updates from upstream ObsidianOS into the local vault.

  • 165 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsgit

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add benoror/obsidianos_work --skill sync-upstream-obsidianos --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sync Upstream Obsidianos?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sync Upstream Obsidianos
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/benoror-sync-upstream-obsidianos/badge)](https://www.skillsdirectory.com/skills/benoror-sync-upstream-obsidianos)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sync-upstream-obsidianos
description: "Pull structural updates from upstream ObsidianOS into the local vault."
license: MIT
---

# Sync Upstream ObsidianOS

Shortcut to run [`.scripts/sync-upstream.sh`](../../../.scripts/sync-upstream.sh).

## Usage

| Command | What it does |
| --- | --- |
| `/sync-upstream-obsidianos` | Preview and merge upstream updates |
| `/sync-upstream-obsidianos preview` | Preview only — show what's new without merging |

## Workflow

### 1. Check prerequisites

- Verify the `obsidianos_work` remote exists: `git remote get-url obsidianos_work`. That is the script's default (`--remote` overrides it). If missing, tell the user to add it and do not create it:
  ```
  git remote add obsidianos_work <url-or-path-to-obsidianos_work>
  ```
  A local checkout works the same as a GitHub URL. The path itself lives in git config, not in this skill.
- Verify working tree is clean (`git status --short`). If dirty, ask the user to commit or stash first.

### 2. Preview

Run `.scripts/sync-upstream.sh --preview` and show the output (new commits and changed files).

If there are no new commits, report "already up to date" and stop.

If the user only asked for `preview`, stop here.

### 3. Confirm and merge

Present the preview results and ask the user to confirm before merging.

On confirmation, run the full sync:

```
echo y | ./.scripts/sync-upstream.sh
```

### 4. Report results

Show the merge outcome:
- Which files were updated.
- Whether any files were excluded via `.sync-exclude`.
- The final commit (`git log -1 --oneline`).

If the merge had conflicts, relay the conflict list and instruct the user to resolve manually.

## Important Notes

- The script protects personal files (Meetings, Teams, Templates, etc.) via `.gitattributes` merge=ours rules.
- Files matching patterns in `.sync-exclude` are auto-removed from the merge (e.g. upstream example files).
- This skill never pushes — the user decides when to push.
- If the `obsidianos_work` remote doesn't exist, do not create it automatically — prompt the user for the URL or local path.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.