Obsidian Sync

Sync repository Markdown files to an Obsidian vault via push_content API.

21|Updated May 18, 2026
One-click install
npx skills add https://github.com/bavanchun/Typeburn --skill obsidian-sync-bavanchun
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: Obsidian Sync
Source: https://github.com/bavanchun/Typeburn/tree/main/.claude/skills/obsidian-sync
Command: npx skills add https://github.com/bavanchun/Typeburn --skill obsidian-sync-bavanchun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncing repository Markdown content to an Obsidian vault enables a centralized reference with a single source of truth, removing manual duplication and drift between your docs and vault.

Core Features & Use Cases

  • Syncs plans and docs Markdown to the Obsidian vault under Projects/Typeburn/.
  • Applies predefined exclusions (e.g., binary wireframes and oversized files) to keep the vault clean.
  • Use Case: Keep your vault up-to-date with planned work and documentation as the repo evolves, without manual exporting.

Quick Start

Run Obsidian Sync to push all Markdown files from plans and docs into the Obsidian vault.

Frequently Asked Questions about Obsidian Sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync markdown files from my repository to an Obsidian vault?โ–ผ

To sync markdown files to an Obsidian vault, this Skill pushes content from the repository's plans and docs directories, creating a one-way mirror under Projects/Typeburn. It uses the Obsidian push_content API to write files while treating the repository as the single source of truth.

Can I sync docs and plans directories automatically without manual exporting?โ–ผ

Yes, you can sync docs and plans markdown automatically without manual exporting. The workflow targets plans/**/*.md and docs/**/*.md paths, writing them directly to the Obsidian vault to keep your reference notes up-to-date as the repository evolves.

Does the sync support two-way updates between the repository and Obsidian vault?โ–ผ

No, the sync does not support two-way updates between the repository and the Obsidian vault. The workflow enforces strict one-way synchronization from the repository to the vault, ensuring only vault-targeted paths are written without any reverse sync.

What file exclusions apply when syncing markdown to the Obsidian vault?โ–ผ

Exclusions applied when syncing markdown to the Obsidian vault include filtering out binary wireframes and oversized files. These predefined path and file size exclusions keep the Obsidian vault clean by preventing non-markdown or excessively large content from being written.

Where are synced markdown files stored within the Obsidian vault?โ–ผ

Synced markdown files are stored within the Obsidian vault under the Projects/Typeburn directory. This specific vault-targeted path receives all mirrored content from the repository's plans and docs folders during the synchronization process.