Agent skill · software engineering · jeremylongshore
evernote-upgrade-migration
Upgrade Evernote SDK versions and migrate between API versions.
Why this skill is useful
Adds a complete migration script and compatibility layer for Evernote SDK upgrades that the AI wouldn't generate on its own.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Evernote Upgrade & Migration Current State !npm list evernote 2>/dev/null echo 'evernote SDK not installed' Overview Guide for upgrading Evernote SDK versions, converting callback-based code to Promises, handling breaking changes, and maintaining backward compatibility during gradual migration. Prerequisites Existing Evernote integration to upgrade Test environment for validation Understanding of current implementation patterns Instructions Step 1: Check Current Version Identify your current SDK version and compare against the latest release. Check the changelog for breaking changes between versions. Step 2: Review Breaking Changes Common breaking changes across Evernote SDK versions: Constructor changes: new Evernote.Note() became new Evernote.Types.Note() Callback to Promise: Older versions used callbacks, newer versions return Promises Import path changes: Module structure may change between major versions Thrift version updates: Underlying Thrift protocol may change serialization Step 3: Convert Callbacks to Promises Wrap callback-based SDK calls in Promise wrappers for modern async/await usage. Step 4: Compatibility Layer Build a compatibility layer that supports both old and new SDK patterns during gradual migration. This allows upgrading module by module instead of a big-bang rewrite. Step 5: Test Suite Updates Update test assertions for new SDK response shapes. Add tests for the compatibility layer. Run both unit and integration tests against the sandbox. Step 6: Deprecation Warnings Add deprecation warnings to old patterns so team members know to use new patterns. Remove after migration is complete. For the full migration script, compatibility layer, test suite updates, and deprecation system, see Implementation Guide. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/evernote-upgrade-migration