[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZNDRY09YA1PQZ7D614KSC":3,"skill-same:01M78ZNDRY09YA1PQZ7D614KSC":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M78ZNDRY09YA1PQZ7D614KSC","evernote-data-handling",null,"Best practices for handling Evernote data.\nUse when implementing data storage, processing notes,\nhandling attachments, or ensuring data integrity.\nTrigger with phrases like \"evernote data\", \"handle evernote notes\",\n\"evernote storage\", \"process evernote content\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--evernote-pack--evernote-data-handling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: evernote-data-handling\ndescription: |\n  Best practices for handling Evernote data.\n  Use when implementing data storage, processing notes,\n  handling attachments, or ensuring data integrity.\n  Trigger with phrases like \"evernote data\", \"handle evernote notes\",\n  \"evernote storage\", \"process evernote content\".\nallowed-tools: Read, Write, Edit, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, evernote, evernote-data]\n---\n# Evernote Data Handling\n\n## Overview\nBest practices for handling Evernote data including ENML content processing, attachment management, local database sync, and ENEX export\u002Fimport.\n\n## Prerequisites\n- Understanding of Evernote data model (Notes, Notebooks, Tags, Resources)\n- Database for local storage (SQLite, PostgreSQL, etc.)\n- File storage for attachments\n\n## Instructions\n\n### Step 1: Data Schema Design\n\nDesign 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.\n\n```sql\nCREATE TABLE notes (\n  guid TEXT PRIMARY KEY,\n  title TEXT NOT NULL,\n  content TEXT,\n  notebook_guid TEXT REFERENCES notebooks(guid),\n  created BIGINT,\n  updated BIGINT,\n  usn INTEGER DEFAULT 0\n);\n```\n\n### Step 2: ENML Content Processing\n\nParse ENML to extract plain text (strip tags), convert to HTML (replace `\u003Cen-note>` with `\u003Cbody>`, resolve `\u003Cen-media>` to `\u003Cimg>`\u002F`\u003Ca>` tags), or convert to Markdown. Validate ENML before sending to the API by checking for required declarations and forbidden elements.\n\n```javascript\nfunction enmlToPlainText(enml) {\n  return enml\n    .replace(\u002F\u003C\\?xml[^>]*\\?>\u002Fg, '')\n    .replace(\u002F\u003C!DOCTYPE[^>]*>\u002Fg, '')\n    .replace(\u002F\u003C[^>]+>\u002Fg, ' ')\n    .replace(\u002F\\s+\u002Fg, ' ')\n    .trim();\n}\n```\n\n### Step 3: Resource (Attachment) Handling\n\nDownload 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.\n\n### Step 4: Sync Data Manager\n\nImplement 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.\n\n```javascript\nconst syncState = await noteStore.getSyncState();\nif (syncState.updateCount > lastSyncUSN) {\n  const chunk = await noteStore.getSyncChunk(lastSyncUSN, 100, true);\n  \u002F\u002F Process chunk.notebooks, chunk.tags, chunk.notes, chunk.resources\n}\n```\n\n### Step 5: Data Export\n\nExport 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.\n\nFor the complete data schema, sync manager, ENML processor, and export implementations, see [Implementation Guide](references\u002Fimplementation-guide.md).\n\n## Output\n- SQL schema for local Evernote data storage\n- ENML-to-text and ENML-to-HTML converters\n- Resource download and local storage manager\n- Incremental sync engine using USN tracking\n- ENEX, JSON, and Markdown export utilities\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `BAD_DATA_FORMAT` | Malformed ENML during update | Validate ENML with DTD check before API call |\n| `QUOTA_REACHED` | Upload limit exceeded | Check `user.accounting.uploaded` before creating notes |\n| `DATA_CONFLICT` | Note modified since last read | Refetch note by GUID and merge changes |\n| Sync chunk gaps | Missed USN range | Request full sync from USN 0 |\n\n## Resources\n- [Evernote Data Model](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fdata_model.php)\n- [ENML Reference](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fenml.php)\n- [Synchronization](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fsynchronization.php)\n- [ENEX Export Format](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fenex.php)\n\n## Next Steps\nFor enterprise features, see `evernote-enterprise-rbac`.\n\n## Examples\n\n**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.\n\n**Markdown export**: Convert all notes in a notebook to Markdown files, preserving folder structure from notebook stacks, and saving attachments to an `assets\u002F` directory.\n","# Evernote Data Handling\n\n## Overview\nBest practices for handling Evernote data including ENML content processing, attachment management, local database sync, and ENEX export\u002Fimport.\n\n## Prerequisites\n- Understanding of Evernote data model (Notes, Notebooks, Tags, Resources)\n- Database for local storage (SQLite, PostgreSQL, etc.)\n- File storage for attachments\n\n## Instructions\n\n### Step 1: Data Schema Design\n\nDesign 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.\n\n```sql\nCREATE TABLE notes (\n  guid TEXT PRIMARY KEY,\n  title TEXT NOT NULL,\n  content TEXT,\n  notebook_guid TEXT REFERENCES notebooks(guid),\n  created BIGINT,\n  updated BIGINT,\n  usn INTEGER DEFAULT 0\n);\n```\n\n### Step 2: ENML Content Processing\n\nParse ENML to extract plain text (strip tags), convert to HTML (replace `\u003Cen-note>` with `\u003Cbody>`, resolve `\u003Cen-media>` to `\u003Cimg>`\u002F`\u003Ca>` tags), or convert to Markdown. Validate ENML before sending to the API by checking for required declarations and forbidden elements.\n\n```javascript\nfunction enmlToPlainText(enml) {\n  return enml\n    .replace(\u002F\u003C\\?xml[^>]*\\?>\u002Fg, '')\n    .replace(\u002F\u003C!DOCTYPE[^>]*>\u002Fg, '')\n    .replace(\u002F\u003C[^>]+>\u002Fg, ' ')\n    .replace(\u002F\\s+\u002Fg, ' ')\n    .trim();\n}\n```\n\n### Step 3: Resource (Attachment) Handling\n\nDownload 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.\n\n### Step 4: Sync Data Manager\n\nImplement 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.\n\n```javascript\nconst syncState = await noteStore.getSyncState();\nif (syncState.updateCount > lastSyncUSN) {\n  const chunk = await noteStore.getSyncChunk(lastSyncUSN, 100, true);\n  \u002F\u002F Process chunk.notebooks, chunk.tags, chunk.notes, chunk.resources\n}\n```\n\n### Step 5: Data Export\n\nExport 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.\n\nFor the complete data schema, sync manager, ENML processor, and export implementations, see [Implementation Guide](references\u002Fimplementation-guide.md).\n\n## Output\n- SQL schema for local Evernote data storage\n- ENML-to-text and ENML-to-HTML converters\n- Resource download and local storage manager\n- Incremental sync engine using USN tracking\n- ENEX, JSON, and Markdown export utilities\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `BAD_DATA_FORMAT` | Malformed ENML during update | Validate ENML with DTD check before API call |\n| `QUOTA_REACHED` | Upload limit exceeded | Check `user.accounting.uploaded` before creating notes |\n| `DATA_CONFLICT` | Note modified since last read | Refetch note by GUID and merge changes |\n| Sync chunk gaps | Missed USN range | Request full sync from USN 0 |\n\n## Resources\n- [Evernote Data Model](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fdata_model.php)\n- [ENML Reference](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fenml.php)\n- [Synchronization](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fsynchronization.php)\n- [ENEX Export Format](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Fenex.php)\n\n## Next Steps\nFor enterprise features, see `evernote-enterprise-rbac`.\n\n## Examples\n\n**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.\n\n**Markdown export**: Convert all notes in a notebook to Markdown files, preserving folder structure from notebook stacks, and saving attachments to an `assets\u002F` directory.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","evernote","evernote-data","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Best practices for handling Evernote data.\nUse when implementing data storage, processing notes,\nhandling attachments, or ensuring data integrity.\nTrigger with phrases like \"evernote data\", \"handle evernote notes\",\n\"evernote storage\", \"process evernote content\".\n","Read, Write, Edit, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--evernote-pack--evernote-data-handling",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill evernote-data-handling",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill evernote-data-handling",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill evernote-data-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--evernote-pack--evernote-data-handling\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]