Agent skill · software engineering · jeremylongshore
obsidian-migration-deep-dive
Execute major Obsidian plugin rewrites and migration strategies.
Why this skill is useful
Adds executable migration scripts for converting various note formats to Obsidian, which the AI wouldn't generate on its own.
What it needs
Requires node installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Obsidian Migration Deep Dive Current State !node --version 2>/dev/null echo 'N/A' !ls .enex .json .zip 2>/dev/null head -10 echo 'No export files in cwd' Overview Migrate notes from Notion, Evernote, Roam Research, Bear, and Apple Notes into Obsidian -- handling attachment relocation, internal link conversion to [[wikilinks]], tag migration, and frontmatter generation. Prerequisites Exported data from the source application (see each section for format) A target Obsidian vault created and opened at least once Node.js 18+ for running migration scripts Backup of source data before starting Instructions Step 1: Pre-Migration Assessment Step 2: Notion Export Migration Notion exports as a zip containing markdown files, CSV databases, and attachments. The markdown uses Notion-style links and has UUIDs appended to filenames. Run it: Step 3: Evernote ENEX Migration ENEX files are XML containing notes with HTML content and embedded attachments (base64). Run it: Step 4: Roam Research JSON Migration Roam exports as JSON with a flat array of pages containing children blocks. Step 5: Bear Notes Migration Bear exports markdown with Bear-specific tags (#tag/subtag#) and image references that need conversion. Step 6: Apple Notes Migration Apple Notes has no native export. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/obsidian-migration-deep-dive