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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A solid, well-organized skill body with executable code and a clean single-reference progressive-disclosure structure. Its main weaknesses are incomplete code in the sync/resource steps and a lack of explicit validation checkpoints in the batch sync workflow.

Suggestions

Add executable code or a concrete helper signature to Step 3 (Resource Handling) instead of a prose description.

Insert explicit validation checkpoints into the sync workflow (e.g., verify chunk USN continuity, retry on partial fetch, confirm resource hashes) before proceeding to the next chunk.

Trim the Prerequisites and Output sections, which restate inferable context, to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concise code blocks and assumes Claude's competence, but sections like Overview, Prerequisites, and Output restate information and add light padding. Not a 3 because Prerequisites ('Understanding of Evernote data model', 'Database for local storage') and the Output list add tokens Claude could infer.	2 / 3
Actionability	Provides concrete SQL schema and JavaScript snippets, but Step 3 (Resource Handling) is purely descriptive with no code and the sync snippet leaves processing as a comment ('// Process chunk.notebooks...'). Not a 3 because key steps are incomplete or pseudocode-like; not a 1 because real executable code is present.	2 / 3
Workflow Clarity	Five steps are clearly sequenced and an Error Handling table gives recovery guidance, but the incremental sync / database batch workflow lacks explicit validation checkpoints (e.g., verify chunk integrity, retry on failure) baked into the flow. Per the rubric, missing validation feedback loops for batch/database operations caps this at 2.	2 / 3
Progressive Disclosure	Body is a concise overview with well-organized sections and a single clearly-signaled one-level-deep reference ('see [Implementation Guide](references/implementation-guide.md)'), confirmed as a real bundle file. Not below 3 because navigation is explicit and content is appropriately split.	3 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-structured description that explicitly covers what the skill does, when to use it, and natural trigger phrases, with a clear Evernote-specific niche. The only weakness is that the capability verbs are somewhat abstract rather than naming concrete operations.

Suggestions

Replace abstract verbs ('handling attachments', 'ensuring data integrity') with concrete actions like 'download attachments and store by MD5 hash, validate ENML, sync incrementally via USN'.

Dimension	Reasoning	Score
Specificity	Lists several domain actions ('implementing data storage, processing notes, handling attachments, or ensuring data integrity') but they are somewhat abstract rather than concrete like 'extract text, fill forms'; not comprehensive. Not a 3 because the actions are generic verbs on Evernote data rather than multiple specific concrete operations.	2 / 3
Completeness	Clearly answers both what ('Best practices for handling Evernote data') and when via an explicit 'Use when...' clause with concrete triggers. Not below 3 because both what and when are explicitly stated rather than implied.	3 / 3
Trigger Term Quality	Provides natural phrases a user would say ('evernote data', 'handle evernote notes', 'evernote storage', 'process evernote content') with good coverage of common variations. Not below 3 because these are realistic user utterances, not technical jargon.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to a distinct Evernote-data niche with Evernote-specific triggers, making conflict with other skills unlikely. Not below 3 because the triggers are domain-anchored and unambiguous.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.