Skip to content
Back to skills

Evernote Upgrade Migration

ASecurity

Upgrade Evernote SDK versions and migrate between API versions. Use when upgrading SDK, handling breaking changes, or migrating to newer API patterns. Trigger with phrases like "upgrade evernote sdk", "evernote migration", "update evernote", "evernote breaking changes".

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
documentationbashgitapici/cd

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill evernote-upgrade-migration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evernote Upgrade Migration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Evernote Upgrade Migration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-evernote-upgrade-migration/badge)](https://www.skillsdirectory.com/skills/micsapp-evernote-upgrade-migration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: evernote-upgrade-migration
description: |
  Upgrade Evernote SDK versions and migrate between API versions.
  Use when upgrading SDK, handling breaking changes,
  or migrating to newer API patterns.
  Trigger with phrases like "upgrade evernote sdk", "evernote migration",
  "update evernote", "evernote breaking changes".
allowed-tools: Read, Write, Edit, Bash(npm:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Evernote Upgrade & Migration

## Overview
Guide for upgrading Evernote SDK versions, handling breaking changes, and migrating legacy integrations to current API patterns.

## Prerequisites
- Existing Evernote integration
- Test environment for validation
- Understanding of current implementation

## Instructions

### Step 1: Check Current Version

### Step 2: Review Breaking Changes

### Step 3: Migration Script

### Step 4: Convert Callbacks to Promises

### Step 5: Upgrade Dependencies

### Step 6: Test Suite Updates

### Step 7: Compatibility Layer

### Step 8: Deprecation Warnings

For full implementation details and code examples, load:
`references/implementation-guide.md`

## Output
- SDK version comparison
- Automated migration script
- Callback to Promise conversion
- Compatibility layer for gradual migration
- Migration test suite
- Deprecation warning system

## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| `Evernote.Note is not a constructor` | Old import style | Use `Evernote.Types.Note` |
| `callback is not a function` | Mixed patterns | Use Promise or callback, not both |
| `Cannot read property 'then'` | Using old callback-only method | Update to Promise-based method |

## Resources
- [Evernote SDK JS](https://github.com/Evernote/evernote-sdk-js)
- [SDK Changelog](https://github.com/Evernote/evernote-sdk-js/releases)
- [API Reference](https://dev.evernote.com/doc/reference/)

## Next Steps
For CI/CD integration, see `evernote-ci-integration`.

## Examples

**Basic usage**: Apply evernote upgrade migration to a standard project setup with default configuration options.

**Advanced scenario**: Customize evernote upgrade migration for production environments with multiple constraints and team-specific requirements.

Files in this skill

  • SKILL.md2.2 KB
  • references/implementation-guide.md8.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.