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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-common-errors80
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
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger terms and clear 'when to use' guidance. The main weakness is the somewhat generic capability statement - it could benefit from listing specific error types or debugging actions it handles. The explicit trigger phrases section is a strong addition that aids skill selection.
Suggestions
Add specific concrete actions like 'resolve authentication errors, handle rate limits, parse EDAMErrorCode responses, fix sync conflicts' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote API) and general actions ('diagnose and fix common errors'), but doesn't list specific concrete actions like 'handle rate limits, resolve authentication failures, parse error codes'. | 2 / 3 |
Completeness | Clearly answers both what ('Diagnose and fix common Evernote API errors') and when ('Use when encountering Evernote API exceptions, debugging failures, or troubleshooting integration issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'evernote error', 'evernote exception', 'fix evernote issue', 'debug evernote', 'evernote troubleshooting' - these match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Evernote API errors - unlikely to conflict with other skills due to the specific product name and error-handling focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable error reference guide with excellent code examples and comprehensive coverage of Evernote API exceptions. The main weaknesses are verbosity (could be more condensed), lack of an explicit diagnostic workflow for identifying error types, and all content being inline rather than using progressive disclosure to separate the quick reference from detailed implementations.
Suggestions
Add an explicit diagnostic workflow at the top: 'When you encounter an error: 1. Check error.errorCode 2. If has parameter → UserException 3. If has rateLimitDuration → SystemException 4. If has identifier → NotFoundException'
Move the detailed EvernoteErrorHandler service class to a separate file (e.g., error-handler-service.md) and reference it from the main skill
Remove the Overview and Prerequisites sections - Claude understands the context from the skill description and doesn't need these explained
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but includes some unnecessary verbosity like the 'Overview' section explaining what the guide covers, and the 'Prerequisites' section stating basic requirements Claude would understand. The error handling service is thorough but could be more condensed. | 2 / 3 |
Actionability | Excellent actionability with fully executable JavaScript code examples for every error type, complete with wrong/correct comparisons, validation functions, and a reusable error handling service class that is copy-paste ready. | 3 / 3 |
Workflow Clarity | While individual error fixes are clear, the overall diagnostic workflow is implicit. There's no explicit 'when you encounter an error, do X then Y' sequence. The retry logic includes validation but lacks a clear troubleshooting flowchart for diagnosing which error type you're facing. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a quick reference table, but the document is quite long (~400 lines) with all content inline. The error handling service and detailed examples could be split into separate reference files, with SKILL.md providing just the quick reference and common fixes. | 2 / 3 |
Total | 9 / 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 | |
- 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.