Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/evernote-data-handling

@820dfc8
Run it yourself

Best practices for handling Evernote data. Use when implementing data storage, processing notes, handling attachments, or ensuring data integrity. Trigger with phrases like "evernote data", "handle evernote notes", "evernote storage", "process evernote content".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/evernote-data-handling

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈72 tokens for metadata: the name and description. ≈976 when used: this file. ≈4.2k more on demand in 1 file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈287 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill processes external Evernote data, which introduces a potential surface for indirect prompt injection attacks, though standard sanitization practices are implemented.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago
What it can do
Reads files Edits files
version
1.13.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "evernote",
  "evernote-data"
]
All 4 allowed tools
ReadWriteEditGrep
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/evernote-data-handling