agentleFS
ntaffziintaffzii/Skill-Agents/skills/obsidian/obsidian-notion-bridge/SKILL.md

obsidian-notion-bridge

Skill4 starsChanged 3 months agoMITView on GitHub

Safely bridge Obsidian Markdown notes and Notion pages while preserving source-of-truth, tags, links, page IDs, URLs, and metadata. Use when the user asks to sync, publish, migrate, convert, summarize, or organize knowledge between Obsidian, Notion, local memory, or RAG indexes.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when knowledge should move between local notes and Notion.

    line 8
  2. Distinctive:

    Prefer Obsidian/local Markdown as source of truth for personal knowledge unless the user says Notion is authoritative.

    line 12
  3. Distinctive:

    Keep Notion updates as draft payloads until explicitly applied.

    line 13
  4. Distinctive:

    Read only selected notes/pages first.

    line 19
  5. Distinctive:

    Use bridge tools to create Notion payload plans or Obsidian Markdown plans.

    line 29
  6. Distinctive:

    Use RAG tools to chunk/index notes only after source metadata is preserved.

    line 30
  7. Distinctive:

    Check links/tags are not silently dropped.

    line 34
  8. Distinctive:

    Call out any lossy conversion.

    line 35
  9. Distinctive:

    Do not mass rename notes.

    line 39
  10. Distinctive:

    Do not auto-delete old notes/pages.

    line 40
  11. Distinctive:

    Do not auto-sync an entire vault without a reviewed plan.

    line 41
  12. Distinctive:

    Keep private notes private unless the user asks to publish or share.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Obsidian Notion Bridge

Use this skill when knowledge should move between local notes and Notion.

Source Of Truth

  • Prefer Obsidian/local Markdown as source of truth for personal knowledge unless the user says Notion is authoritative.
  • Keep Notion updates as draft payloads until explicitly applied.
  • Preserve source paths, Notion page IDs, Notion URLs, tags, aliases, and wikilinks.

Workflow

  1. Inspect selected scope.
    • Read only selected notes/pages first.
    • Extract title, tags, wikilinks, frontmatter, URLs, and IDs.
  2. Plan mapping.
    • Obsidian heading -> Notion page title.
    • Obsidian tags -> Notion multi-select/tag property.
    • Wikilinks -> text references unless a target page map exists.
    • Notion page ID/URL -> Markdown frontmatter.
  3. Draft conversion.
    • Use bridge tools to create Notion payload plans or Obsidian Markdown plans.
    • Use RAG tools to chunk/index notes only after source metadata is preserved.
  4. Verify.
    • Check frontmatter validity.
    • Check links/tags are not silently dropped.
    • Call out any lossy conversion.

Safety

  • Do not mass rename notes.
  • Do not auto-delete old notes/pages.
  • Do not auto-sync an entire vault without a reviewed plan.
  • Keep private notes private unless the user asks to publish or share.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.