CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-common-errors

Diagnose and fix common Evernote API errors. Use when encountering Evernote API exceptions, debugging failures, or troubleshooting integration issues. Trigger with phrases like "evernote error", "evernote exception", "fix evernote issue", "debug evernote", "evernote troubleshooting".

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.

Actionable, well-structured content with good progressive disclosure and executable examples. It is held back by some redundant sections and the absence of an explicit end-to-end diagnostic workflow with validation checkpoints.

Suggestions

Remove or merge the "Error Handling" table and "Output" section, which duplicate the Overview and per-section guidance, to improve conciseness.

Add an explicit diagnostic workflow (e.g., 1. identify exception type, 2. look up code, 3. apply fix, 4. validate the result) with validation checkpoints to lift workflow clarity.

Consolidate the three exception types into a single triage sequence so the handling patterns form one coherent process rather than parallel reference blocks.

DimensionReasoningScore

Conciseness

The body is mostly lean tables and code, but the "Error Handling" table and "Output" section restate information already covered in the Overview and per-section content, so it could be tightened.

2 / 3

Actionability

It provides complete, executable JavaScript (validateENML, withRetry, safeGetNote) alongside a concrete error-code reference table — copy-paste ready guidance.

3 / 3

Workflow Clarity

Per-error handling patterns and a retry-with-backoff feedback loop are present, but there is no unified diagnostic sequence with explicit validation checkpoints tying the cases together.

2 / 3

Progressive Disclosure

The SKILL.md is a well-organized overview with clearly signaled, one-level-deep navigation to references/implementation-guide.md (a real file) for the full ErrorHandler class.

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 description with explicit trigger guidance and a clear, distinctive Evernote API niche. The only weakness is that the capability statement is somewhat general rather than enumerating concrete actions.

DimensionReasoningScore

Specificity

"Diagnose and fix common Evernote API errors" names the domain and a couple of actions, but it is not a list of multiple specific concrete actions, so it stops short of the top anchor.

2 / 3

Completeness

It states what the skill does ("Diagnose and fix common Evernote API errors") and gives explicit "Use when..." guidance plus trigger phrases, covering both what and when.

3 / 3

Trigger Term Quality

It lists natural phrases a user would say — "evernote error", "evernote exception", "fix evernote issue", "debug evernote", "evernote troubleshooting" — giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Evernote-specific scope and "evernote"-prefixed triggers make it a clear niche 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.