evernote-data-handling
Best practices for handling Evernote data. Use when implementing data storage, processing notes, handling attachments, or ensuring data integrity. Trigger with phrases like "evernote data", "handle evernote notes", "evernote storage", "process evernote content".
61
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/evernote-pack/skills/evernote-data-handling/SKILL.mdQuality
Discovery
57%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has good structural completeness with explicit 'Use when' and 'Trigger with' clauses, but suffers from vague, abstract language that doesn't convey concrete capabilities. The Evernote branding provides some distinctiveness, but the actual actions described are too generic to clearly communicate what the skill does or differentiate it from general data handling skills.
Suggestions
Replace vague phrases like 'best practices for handling Evernote data' with specific concrete actions such as 'Parse ENEX export files, extract note content and metadata, convert Evernote notebooks to markdown, handle embedded resources and attachments'.
Add more natural trigger terms users would actually say, such as 'ENEX files', 'export from Evernote', 'migrate Evernote notes', 'Evernote backup', '.enex'.
Make the 'what' portion more distinctive by specifying Evernote-specific operations rather than generic data handling terms like 'data storage' and 'data integrity'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'best practices for handling Evernote data' which is vague. Actions like 'data storage', 'processing notes', 'handling attachments', and 'ensuring data integrity' are generic and abstract rather than concrete specific actions (e.g., no mention of parsing ENEX files, extracting note metadata, converting formats, etc.). | 1 / 3 |
Completeness | The description answers both 'what' (best practices for handling Evernote data, storage, processing notes, handling attachments, data integrity) and 'when' with explicit trigger phrases and a 'Use when...' clause. Despite the vagueness of the 'what', both components are present and explicit. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'evernote data', 'evernote notes', 'evernote storage', 'process evernote content', and 'attachments'. However, it misses common variations users might say such as 'ENEX', 'export notes', 'import evernote', 'note migration', or specific file formats. | 2 / 3 |
Distinctiveness Conflict Risk | The Evernote-specific terms help distinguish it, but phrases like 'data storage', 'processing notes', 'handling attachments', and 'data integrity' are generic enough to overlap with general note-taking, data handling, or attachment processing skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of Evernote data handling with some useful code snippets and a clear error handling table. However, it falls short on actionability—several steps are descriptive rather than executable—and lacks validation checkpoints critical for sync and database operations. The referenced implementation guide doesn't exist in the bundle, undermining the progressive disclosure strategy.
Suggestions
Add executable code examples for Step 3 (resource download/storage) and Step 5 (ENEX export), or provide them in the referenced implementation-guide.md bundle file.
Add explicit validation checkpoints: verify resource MD5 after download, validate database state after sync chunk processing, and include a retry/recovery loop for sync failures.
Trim the prerequisites and overview sections—Claude doesn't need to be told what the Evernote data model consists of. Jump straight to the schema design.
Either include the referenced 'references/implementation-guide.md' as a bundle file or remove the reference and inline the critical implementation details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., listing what tables should contain when Claude already understands data modeling, explaining what ENML is). The overview and prerequisites sections add little value. However, it's not egregiously verbose—most sections are reasonably tight. | 2 / 3 |
Actionability | Some concrete code examples are provided (SQL schema, ENML parser, sync chunk), but several steps are vague descriptions rather than executable guidance (Step 3 has no code, Step 5 is purely descriptive). The examples section at the end describes scenarios without providing implementation code. | 2 / 3 |
Workflow Clarity | Steps are sequenced logically (schema → content processing → resources → sync → export), but there are no validation checkpoints or feedback loops. For a multi-step process involving data sync and database operations, the lack of explicit verification steps (e.g., validate sync state after processing chunks, verify resource integrity after download) is a notable gap. | 2 / 3 |
Progressive Disclosure | The skill references an implementation guide at 'references/implementation-guide.md' and links to external Evernote docs, which is good structure. However, no bundle files are provided, meaning the referenced implementation guide doesn't exist. The main content also includes inline details (full SQL schema, error table) that could be split out, while Step 3 and Step 5 lack the detail that should either be inline or clearly delegated. | 2 / 3 |
Total | 8 / 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.