CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-upgrade-migration

Upgrade Evernote SDK versions and migrate between API versions. Use when upgrading SDK, handling breaking changes, or migrating to newer API patterns. Trigger with phrases like "upgrade evernote sdk", "evernote migration", "update evernote", "evernote breaking changes".

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.

A well-structured, actionable migration guide with concrete code and a real one-level reference. It loses points on conciseness (minor redundancy) and workflow_clarity (no explicit validation feedback loop for the destructive/batch aspects of SDK migration).

Suggestions

Tighten conciseness by dropping the Overview paragraph (it restates the description) and trimming the EvernoteCompat class to the minimal illustrative method.

Strengthen workflow_clarity by adding an explicit validate→fix→retry loop after Step 5, e.g. 'Run tests; on failure, revisit the changed module and re-run until green before removing the compatibility layer.'

Make Step 6 (Deprecation Warnings) actionable with a short code snippet instead of a one-line instruction, or explicitly defer it into the implementation guide.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explaining fluff (no explaining what a Promise or Evernote is), but the Overview restates the description's intro and the EvernoteCompat code block is lengthy enough that the body could be tightened further.

2 / 3

Actionability

Provides concrete, executable guidance throughout — specific npm commands ('npm list evernote', 'npm view evernote version'), a runnable callback-to-Promise before/after, and a complete EvernoteCompat class — copy-paste ready.

3 / 3

Workflow Clarity

Steps 1–6 are clearly sequenced and Step 5 names a validation checkpoint ('Run both unit and integration tests against the sandbox') plus an error-recovery table, but there is no explicit validate→fix→retry feedback loop for a migration that touches SDK versions.

2 / 3

Progressive Disclosure

The body is a concise overview that points to a single clearly-signaled, one-level-deep reference ('see [Implementation Guide](references/implementation-guide.md)') which exists as a real file, splitting detail appropriately.

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.

A strong, third-person description with explicit what/when structure and natural trigger phrases. The only weak spot is specificity, since several concrete capabilities from the body are not surfaced in the description.

DimensionReasoningScore

Specificity

Names the Evernote SDK domain and concrete actions ('Upgrade Evernote SDK versions and migrate between API versions', 'handling breaking changes'), but does not surface the fuller capability set (callback-to-Promise conversion, compatibility layer, deprecation warnings) that the body later reveals.

2 / 3

Completeness

Explicitly answers both what ('Upgrade Evernote SDK versions and migrate between API versions') and when ('Use when upgrading SDK, handling breaking changes, or migrating to newer API patterns'), with an explicit 'Use when' clause and trigger phrases.

3 / 3

Trigger Term Quality

Includes natural phrases users would actually say — 'upgrade evernote sdk', 'evernote migration', 'update evernote', 'evernote breaking changes' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Evernote-specific niche with distinct triggers, making it unlikely to fire for unrelated skills.

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.