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".
70
64%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/evernote-pack/skills/evernote-migration-deep-dive/SKILL.mdQuality
Discovery
79%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 has strong trigger terms, explicit 'Use when' guidance, and a clear niche, but it fails to describe any concrete actions or capabilities beyond the vague 'deep dive into strategies.' It reads more like a topic label than a capability description, leaving Claude unsure what specific operations this skill can actually perform.
Suggestions
Replace 'Deep dive into Evernote data migration strategies' with specific actions like 'Exports notes from Evernote in ENEX format, converts notebooks for import into other platforms, maps tags and metadata, handles bulk note transfers.'
Add concrete output types or deliverables, e.g., 'Generates migration plans, converts file formats, validates data integrity after transfer.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'deep dive into Evernote data migration strategies' but never lists concrete actions like 'export notes', 'convert ENEX files', 'map tags', or 'transfer attachments'. 'Deep dive' and 'strategies' are vague and abstract. | 1 / 3 |
Completeness | It answers both 'what' (Evernote data migration strategies) and 'when' (explicit 'Use when' clause with migration scenarios, plus explicit trigger phrases). Both components are present and clearly stated. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases like 'migrate to evernote', 'migrate from evernote', 'evernote data transfer', 'bulk evernote migration' which are terms users would naturally say. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Evernote migration is a very specific niche. The triggers are clearly scoped to Evernote and migration scenarios, making it unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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.
The skill provides a reasonable structure for Evernote migration with some useful code examples and a helpful error handling table. However, it suffers from incomplete actionability (Steps 3-4 lack code), references a non-existent implementation guide, and misses explicit validation checkpoints critical for bulk data migration operations. The content could be more concise by trimming obvious prerequisites and overview prose.
Suggestions
Add executable code for Steps 3 and 4 (ENML import and migration runner with checkpointing), or at minimum provide the referenced implementation-guide.md bundle file.
Add explicit validation checkpoints with code: e.g., a verification function that compares source/target note counts and content hashes, with a retry loop on mismatch.
Remove the Prerequisites section (Claude already knows the Evernote data model) and trim the Overview to a single sentence to improve conciseness.
Provide concrete code in the Examples section rather than prose descriptions of what the code would do.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary padding (e.g., 'Comprehensive guide for migrating data to and from Evernote' overview, the Prerequisites section listing things Claude already knows like 'Understanding of Evernote data model'). The code examples earn their place, but the prose around them could be tighter. | 2 / 3 |
Actionability | Steps 1 and 2 have executable JavaScript code, but Steps 3 and 4 are vague prose with no code ('Convert source data to ENML format...', 'Build a migration runner...'). The examples section describes what to do without providing executable code. Key implementation is deferred to a reference file that doesn't exist in the bundle. | 2 / 3 |
Workflow Clarity | The four steps provide a logical sequence, and the error handling table is useful. However, validation/verification is mentioned only in passing ('Verify each import by comparing note counts and content hashes') without concrete commands or code. For a destructive/bulk migration operation, the lack of explicit validation checkpoints with feedback loops caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill references an implementation guide at 'references/implementation-guide.md', which is a good structural choice, but no bundle files exist to support this reference. The main file itself is moderately well-organized with clear sections, but critical implementation details are deferred to a non-existent file, making the reference a dead end. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.