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' could be more specific about the concrete actions performed (e.g., listing specific error types handled or resolution strategies). Overall it's a solid description that would perform well in skill selection.
Suggestions
Add specific concrete actions beyond 'diagnose and fix', such as 'resolve authentication errors, handle rate limiting, parse EDAMErrorCode responses, fix sync conflicts'.
| 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 API 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 errors specifically. Unlikely to conflict with other skills given the narrow, product-specific 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 reference skill with good actionable code examples and a useful error code table. Its main weaknesses are some redundancy (the Output and Error Handling sections largely restate earlier content) and the lack of an explicit diagnostic workflow that sequences how to identify and resolve an unknown error. The code examples are executable and practical, which is the skill's strongest aspect.
Suggestions
Add an explicit diagnostic workflow at the top: 'When you encounter an error: 1. Identify exception type, 2. Look up error code in table, 3. Apply the corresponding fix pattern, 4. Validate and retry'
Remove the redundant 'Output' section and 'Error Handling' table, which restate information already covered in the body
Move the detailed error code table and ENML validation function to a reference file, keeping only the most common cases inline
| 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. The Examples section at the end describes workflows rather than showing executable code. | 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 an unknown error (e.g., 'first check exception type, then look up code, then apply fix'). The ENML debugging example mentions running validateENML() but doesn't show a validate-fix-retry loop. The centralized error handler is deferred to a reference file without showing the classification logic. | 2 / 3 |
Progressive Disclosure | There is one reference to an implementation guide for the centralized error handler and external resource links, which is good. However, the skill itself is fairly long with inline content that could be split (e.g., the full error code table and ENML validation could be in separate reference files), and the reference to 'evernote-debug-bundle' in Next Steps is vague without a clear path. | 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
3e83543
- 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.