Agent skill · marketing growth · jeremylongshore
evernote-migration-deep-dive
Deep dive into Evernote data migration strategies.
Why this skill is useful
Provides detailed migration strategies and scripts for Evernote that the AI wouldn't reliably generate on its own.
What it needs
Requires evernote account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Evernote Migration Deep Dive Current State !npm list 2>/dev/null head -5 Overview Comprehensive guide for migrating data to and from Evernote, including ENEX export/import, bulk API operations, format conversions (ENML to Markdown, HTML to ENML), and data integrity verification. Prerequisites Understanding of Evernote data model (Notes, Notebooks, Tags, Resources) Source/target system access credentials Sufficient API quota for migration volume Backup strategy in place before starting Instructions Step 1: Migration Planning Assess the migration scope: count notes, notebooks, tags, and total resource size. Estimate API call count and quota consumption. Plan for rate limits (add delays between operations). Step 2: Export from Evernote Export notes in three formats: ENEX (Evernote's XML format, preserves everything including resources), JSON (structured data for programmatic use), or Markdown (human-readable, loses some formatting). Step 3: Import to Evernote Convert source data to ENML format, create notebooks to match source structure, and bulk-create notes with rate limit handling. Verify each import by comparing note counts and content hashes. Step 4: Migration Runner Build a migration runner with progress tracking, checkpointing (resume from failure), and verification. Log every operation for audit trail. For the full migration planner, ENEX parser, format converters, migration runner, and verification tools, see Implementation Guide. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/evernote-migration-deep-dive