evernote-migration-deep-dive
Deep dive into Evernote data migration strategies. Use when migrating to/from Evernote, bulk data transfers, or complex migration scenarios. Trigger with phrases like "migrate to evernote", "migrate from evernote", "evernote data transfer", "bulk evernote migration".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-migration-deep-diveOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
63%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger terms and distinctiveness with explicit Evernote-focused phrases, but fails to describe concrete actions the skill performs. 'Deep dive into strategies' is vague fluff that doesn't tell Claude what capabilities this skill provides (e.g., export formats, API interactions, data mapping).
Suggestions
Replace 'Deep dive into Evernote data migration strategies' with specific actions like 'Export notes from Evernote, convert ENEX files, map notebooks to target formats, handle attachments and tags'
Add concrete capabilities such as 'Supports migration to/from OneNote, Notion, plain markdown, or local backup formats'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'deep dive' and 'strategies' without listing concrete actions. It doesn't specify what the skill actually does (e.g., export notes, convert formats, map data structures). | 1 / 3 |
Completeness | Has explicit 'Use when' and 'Trigger with' clauses addressing when to use it, but the 'what' is weak - 'deep dive into strategies' doesn't explain concrete capabilities or actions performed. | 2 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'migrate to evernote', 'migrate from evernote', 'evernote data transfer', 'bulk evernote migration'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Evernote migrations specifically with distinct triggers. Unlikely to conflict with general document or data migration skills due to explicit Evernote focus. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable migration code but severely violates token efficiency by including hundreds of lines of implementation details that Claude could generate contextually. The workflow has good structure but lacks explicit validation checkpoints for what is a destructive batch operation. The content would be far more effective as a concise overview with references to separate implementation files.
Suggestions
Extract the large class implementations into separate reference files (e.g., EXPORTER.md, IMPORTER.md) and keep only a concise overview with key patterns in the main skill
Add explicit validation checkpoints between migration phases with concrete verification commands (e.g., 'Verify export: count files in output directory matches source note count')
Implement the verify() method with actual verification logic rather than a stub, as this is critical for data migration integrity
Reduce the ENML-to-Markdown conversion to a brief example or reference, as Claude can generate regex transformations on demand
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with ~500+ lines of code. Much of this is boilerplate that Claude could generate on demand. The extensive class implementations explain patterns Claude already knows (async iteration, file I/O, hash computation). | 1 / 3 |
Actionability | Provides fully executable JavaScript code with complete class implementations, specific API calls, and copy-paste ready examples. The code is concrete and functional, not pseudocode. | 3 / 3 |
Workflow Clarity | Steps are numbered (1-4) and there's a migration checklist, but validation checkpoints are implicit rather than explicit. The verify() method is a stub returning hardcoded success, missing actual verification logic for this destructive batch operation. | 2 / 3 |
Progressive Disclosure | Has some structure with sections and a checklist, but the massive code blocks should be in separate reference files. The skill would benefit from a concise overview pointing to detailed implementation files rather than inline walls of code. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
69%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (776 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.