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".
80
77%
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-common-errors/SKILL.mdQuality
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 strong trigger terms, clear 'when' guidance, and a distinct niche. Its main weakness is that the 'what' portion is somewhat general — it could benefit from listing specific types of errors or fixes it handles to improve specificity.
Suggestions
Add specific concrete actions such as 'resolve authentication errors, handle rate limiting, parse EDAMUserException and EDAMSystemException codes, fix sync conflicts' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Evernote API errors) and some actions ('diagnose and fix'), but doesn't list specific concrete actions like parsing error codes, handling rate limits, resolving auth failures, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix common Evernote API errors) and 'when' (encountering exceptions, debugging failures, troubleshooting integration issues), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'evernote error', 'evernote exception', 'fix evernote issue', 'debug evernote', 'evernote troubleshooting' — these are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Evernote API error handling is highly specific and unlikely to conflict with other skills. The trigger terms are all Evernote-specific. | 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 skill provides solid, actionable error reference material with executable code examples and a useful error code table. Its main weaknesses are some redundancy between sections (the Error Handling table duplicates the overview, the Output section restates content), a lack of an explicit diagnostic workflow with validation checkpoints, and references to bundle files that don't exist.
Suggestions
Add an explicit diagnostic workflow sequence: 'Step 1: Identify exception type → Step 2: Look up error code → Step 3: Apply fix → Step 4: Verify fix worked' with validation checkpoints.
Remove the redundant 'Output' and 'Error Handling' sections since they restate information already covered in the body, or consolidate them into the existing content.
Either provide the referenced 'references/implementation-guide.md' bundle file or inline the essential parts of the EvernoteErrorHandler class.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but includes some unnecessary sections like 'Prerequisites' (Claude knows Evernote SDK basics), the 'Output' section which just restates what was already covered, and the 'Error Handling' table which largely duplicates the overview paragraph. Could be tightened. | 2 / 3 |
Actionability | Provides fully executable JavaScript code for ENML validation, retry logic with rate limit handling, and safe getter patterns. The error code table gives specific codes, causes, and fixes. Code is copy-paste ready and covers the main error scenarios concretely. | 3 / 3 |
Workflow Clarity | Individual error handling patterns are clear, but there's no explicit sequenced workflow for diagnosing errors (e.g., 'first check exception type, then look up code, then apply fix, then verify'). The ENML validation example in the Examples section hints at a workflow but lacks explicit validation checkpoints or feedback loops for the overall debugging process. | 2 / 3 |
Progressive Disclosure | References an implementation guide at 'references/implementation-guide.md' and an 'evernote-debug-bundle', but no bundle files are provided, making these references unverifiable. The main content is reasonably structured with headers but includes some sections (Output, Error Handling table) that add bulk without clear navigational purpose. External resource links are helpful. | 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 | |
- 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.