evernote-data-handling
Learn patterns for storing, parsing, and syncing Evernote notes, resources, and ENML content.
Install
mkdir -p .claude/skills/evernote-data-handling && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7112" && unzip -o skill.zip -d .claude/skills/evernote-data-handling && rm skill.zipInstalls to .claude/skills/evernote-data-handling
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Best practices for handling Evernote data.Key capabilities
- →Design local database schemas for Evernote data
- →Parse and convert ENML content
- →Manage attachments and resources
- →Implement incremental sync using USN
- →Export notes to ENEX, JSON, or Markdown
How it works
It defines a local database schema and provides utilities for syncing data chunks, processing ENML, and managing binary attachments.
Inputs & outputs
When to use evernote-data-handling
- →Design a local database schema for notes
- →Process and convert ENML content
- →Implement incremental sync with USN
- →Manage note attachments and resources
About this skill
Evernote Data Handling
Overview
Best practices for handling Evernote data including ENML content processing, attachment management, local database sync, and ENEX export/import.
Prerequisites
- Understanding of Evernote data model (Notes, Notebooks, Tags, Resources)
- Database for local storage (SQLite, PostgreSQL, etc.)
- File storage for attachments
Instructions
Step 1: Data Schema Design
Design a local database schema that mirrors Evernote's data model. Key tables: notes (guid, title, content, notebookGuid, created, updated, USN), notebooks (guid, name, stack), tags (guid, name), resources (guid, noteGuid, mime, hash, size). Track Update Sequence Numbers (USN) for incremental sync.
CREATE TABLE notes (
guid TEXT PRIMARY KEY,
title TEXT NOT NULL,
content TEXT,
notebook_guid TEXT REFERENCES notebooks(guid),
created BIGINT,
updated BIGINT,
usn INTEGER DEFAULT 0
);
Step 2: ENML Content Processing
Parse ENML to extract plain text (strip tags), convert to HTML (replace <en-note> with <body>, resolve <en-media> to <img>/<a> tags), or convert to Markdown. Validate ENML before sending to the API by checking for required declarations and forbidden elements.
function enmlToPlainText(enml) {
return enml
.replace(/<\?xml[^>]*\?>/g, '')
.replace(/<!DOCTYPE[^>]*>/g, '')
.replace(/<[^>]+>/g, ' ')
.replace(/\s+/g, ' ')
.trim();
}
Step 3: Resource (Attachment) Handling
Download resources via noteStore.getResource(guid, withData, ...). Store binary data locally with the MD5 hash as filename. Track MIME types for proper content-type serving. Compute hashes for integrity verification.
Step 4: Sync Data Manager
Implement incremental sync using getSyncState() to get the current server USN, then getSyncChunk() to fetch changes since your last sync. Process chunks in order: notebooks first, then tags, then notes, then resources.
const syncState = await noteStore.getSyncState();
if (syncState.updateCount > lastSyncUSN) {
const chunk = await noteStore.getSyncChunk(lastSyncUSN, 100, true);
// Process chunk.notebooks, chunk.tags, chunk.notes, chunk.resources
}
Step 5: Data Export
Export notes to ENEX (Evernote's XML export format), JSON, or Markdown. ENEX preserves the full note structure including resources and is compatible with Evernote import.
For the complete data schema, sync manager, ENML processor, and export implementations, see Implementation Guide.
Output
- SQL schema for local Evernote data storage
- ENML-to-text and ENML-to-HTML converters
- Resource download and local storage manager
- Incremental sync engine using USN tracking
- ENEX, JSON, and Markdown export utilities
Error Handling
| Error | Cause | Solution |
|---|---|---|
BAD_DATA_FORMAT | Malformed ENML during update | Validate ENML with DTD check before API call |
QUOTA_REACHED | Upload limit exceeded | Check user.accounting.uploaded before creating notes |
DATA_CONFLICT | Note modified since last read | Refetch note by GUID and merge changes |
| Sync chunk gaps | Missed USN range | Request full sync from USN 0 |
Resources
- Evernote Data Model
- ENML Reference
- Synchronization
- ENEX Export Format
Next Steps
For enterprise features, see evernote-enterprise-rbac.
Examples
Local mirror: Sync all notes to a local SQLite database using incremental sync. Store resources on disk keyed by MD5 hash. Use the local mirror for full-text search without API calls.
Markdown export: Convert all notes in a notebook to Markdown files, preserving folder structure from notebook stacks, and saving attachments to an assets/ directory.
Prerequisites
Limitations
- →Requires local database and file storage setup
- →Sync chunk gaps require full re-sync
How it compares
It provides a structured approach to local mirroring and USN-based synchronization instead of manual API polling.
Compared to similar skills
evernote-data-handling side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| evernote-data-handling (this skill) | 1 | 26d | No flags | Advanced |
| backend-development | 17 | 4mo | No flags | Intermediate |
| using-neon | 1 | 6mo | Review | Intermediate |
| backend-patterns | 0 | 1mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
backend-development
skillcreatorai
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
using-neon
davila7
Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
backend-patterns
chenqin231
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
sql-optimization-patterns
wshobson
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
drizzle-orm
EpicenterHQ
Drizzle ORM patterns for type branding and custom types. Use when working with Drizzle column definitions, branded types, or custom type conversions.
postgres-patterns
affaan-m
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.