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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-data-handling79
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 description has strong completeness with explicit 'Use when' and 'Trigger with' clauses, and good distinctiveness through Evernote-specific terminology. However, the capabilities described are somewhat vague ('best practices', 'handling', 'ensuring data integrity') rather than listing concrete actions like 'import notes', 'export to ENEX', or 'parse note metadata'.
Suggestions
Replace vague terms like 'best practices' and 'handling' with specific concrete actions (e.g., 'Import/export ENEX files, parse note metadata, extract embedded attachments')
Add specific file formats or technical details that would help distinguish capabilities (e.g., '.enex files', 'note XML structure', 'attachment MIME types')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote data) and mentions some actions like 'data storage', 'processing notes', 'handling attachments', and 'ensuring data integrity', but these are fairly generic and not concrete specific actions like 'extract', 'merge', or 'convert'. | 2 / 3 |
Completeness | Clearly answers both what ('Best practices for handling Evernote data' with storage, processing, attachments, data integrity) and when ('Use when implementing data storage, processing notes...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'evernote data', 'handle evernote notes', 'evernote storage', 'process evernote content'. Good coverage of natural variations around Evernote-specific terminology. | 3 / 3 |
Distinctiveness Conflict Risk | The Evernote-specific focus creates a clear niche that is unlikely to conflict with generic document or note-taking skills. The explicit 'evernote' keyword throughout makes it distinctly identifiable. | 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 comprehensive, executable code for Evernote data handling with strong actionability through complete SQL schemas and JavaScript implementations. However, it suffers from being overly long without proper progressive disclosure, and lacks explicit validation checkpoints for critical operations like sync processing and data deletion that could cause data integrity issues.
Suggestions
Add explicit validation steps within workflows, especially before data deletion operations (e.g., 'Verify user exists before deletion', 'Confirm sync state before processing chunk')
Split the large code blocks into separate reference files (e.g., SCHEMA.sql, enml-processor.js, sync-manager.js) and keep only quick-start examples in the main skill
Remove the prerequisites section and overview - Claude understands Evernote's data model and doesn't need the preamble
Add error recovery guidance for sync failures and partial data states
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial code examples but includes some unnecessary verbosity like the overview section and prerequisites that Claude would already understand. The data model diagram is helpful but the overall content could be tightened. | 2 / 3 |
Actionability | Excellent executable code throughout - complete SQL schema, fully functional JavaScript classes with proper imports, and copy-paste ready implementations for ENML processing, resource handling, sync management, and data export. | 3 / 3 |
Workflow Clarity | Steps are numbered and organized, but validation checkpoints are missing for critical operations like database migrations, sync processing, and data deletion. The checklist at the end is helpful but doesn't integrate validation into the workflow steps themselves. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the skill is monolithic with ~400 lines of code that could be split into separate reference files. The 'Next Steps' reference to enterprise features is good, but inline code blocks could be externalized. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (715 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 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.