CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and well-structured with a clean one-level-deep reference, but actionability is uneven because the import and runner steps are prose-only in the body, and the batch workflow lacks an explicit validate-fix-retry feedback loop.

Suggestions

Add an executable code snippet for Step 3 (Import to Evernote) and Step 4 (Migration Runner) in the body, or at minimum a concrete command/function signature, instead of deferring entirely to the reference.

Make the validation feedback loop explicit in the body (e.g., 'after each batch: verify counts/hashes; on mismatch: restore from checkpoint, fix, re-run') rather than only describing checkpointing as a feature.

Tighten the format-descriptions in Step 2 (ENEX/JSON/Markdown parentheticals) to remove minor explanatory padding of formats Claude largely already knows.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it avoids explaining what Evernote is and uses compact code, an error table, and short examples where every token earns its place, matching anchor 3.

3 / 3

Actionability

Steps 1 and 2 provide executable JavaScript, but Steps 3 and 4 are descriptive prose ('Convert source data to ENML...', 'Build a migration runner...') with no executable code in the body, deferring details to the reference, matching anchor 2 rather than 3.

2 / 3

Workflow Clarity

The four steps are clearly sequenced and verification is mentioned ('Verify each import by comparing note counts and content hashes'), but the body lacks an explicit validate-fix-retry feedback loop for this batch/destructive operation, which the guidelines cap at 2.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview that defers full details to a single well-signaled one-level-deep reference ('see [Implementation Guide](references/implementation-guide.md)') which exists, matching anchor 3.

3 / 3

Total

10

/

12

Passed

Description

90%

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 is well-structured with explicit 'Use when' triggers and natural trigger phrases, giving it strong completeness, trigger quality, and distinctiveness. Its only weakness is specificity, since 'deep dive' and 'strategies' are somewhat abstract rather than naming concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ('Evernote data migration') and some actions ('bulk data transfers', 'complex migration scenarios'), but 'deep dive' and 'strategies' are abstract and it lacks multiple concrete specific actions, matching anchor 2 rather than 3.

2 / 3

Completeness

It explicitly answers what ('Evernote data migration strategies', 'bulk data transfers') and when with an explicit 'Use when...' clause and trigger phrases, matching anchor 3.

3 / 3

Trigger Term Quality

It lists natural trigger phrases users would say ('migrate to evernote', 'migrate from evernote', 'evernote data transfer', 'bulk evernote migration'), giving good coverage matching anchor 3.

3 / 3

Distinctiveness Conflict Risk

'Evernote' is a clear niche with distinct triggers unlikely to overlap with other skills, matching anchor 3.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.