CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-sdk-patterns

Advanced Evernote SDK patterns and best practices. Use when implementing complex note operations, batch processing, search queries, or optimizing SDK usage. Trigger with phrases like "evernote sdk patterns", "evernote best practices", "evernote advanced", "evernote batch operations".

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is a well-organized, token-efficient overview that defers detail to one real reference file. Its weak spots are incomplete in-body actionability for three of five patterns and the absence of explicit validation checkpoints for batch/destructive operations.

Suggestions

Add minimal executable code stubs for Patterns 3 (error wrapper) and 4 (batch processor) so the body is actionable without requiring the reference, or explicitly mark them as 'see reference for full implementation'.

Add an explicit validate-then-retry checkpoint to the batch operation pattern (e.g., verify each write succeeded before advancing, and re-fetch on DATA_CONFLICT) to lift workflow clarity.

Trim the 'Output' section, which restates the patterns above, to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is lean: it leads with code, a compact error table, and brief pattern descriptions, and it never pads with concepts Claude already knows (no preamble on what Evernote or an SDK is).

3 / 3

Actionability

Patterns 1 and 2 provide full executable code, but Patterns 3, 4, and 5 are prose-only ('Wrap API calls to distinguish EDAMUserException...', 'Process items sequentially with configurable delay...') with no copy-paste-ready implementation in the body, so it is not score 3 yet well above score 1.

2 / 3

Workflow Clarity

This is a patterns catalog rather than a sequenced workflow, so there are no explicit validation checkpoints; the batch pattern's rate-limit retry is a feedback loop, but batch writes and note updates lack a validate-fix-retry cycle, capping this at 2 per the destructive-operations guideline.

2 / 3

Progressive Disclosure

The body is a clear overview organized into labeled sections and defers full implementations to a single, clearly signaled, one-level-deep reference (references/implementation-guide.md, verified present) rather than nesting references.

3 / 3

Total

10

/

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.

The description is well-structured, explicitly pairing a clear capability statement with a 'Use when' trigger clause and concrete trigger phrases. The main weakness is mild abstraction in two of the listed actions.

Suggestions

Replace the abstract phrases 'complex note operations' and 'optimizing SDK usage' with concrete actions (e.g., 'search notes with NoteFilter, attach files via ENML, batch-create tags with rate-limit retry') to raise specificity.

Consider adding 'evernote api' or 'evernote automation' as additional natural trigger variations for broader coverage.

DimensionReasoningScore

Specificity

It names the domain and several actions ('complex note operations, batch processing, search queries, or optimizing SDK usage'), but 'complex note operations' and 'optimizing SDK usage' are abstract rather than the concrete, enumerated actions of a score-3 anchor.

2 / 3

Completeness

It explicitly states what it does ('Advanced Evernote SDK patterns and best practices') and when to use it ('Use when implementing complex note operations, batch processing, search queries...') with explicit trigger phrases, answering both what and when.

3 / 3

Trigger Term Quality

It lists natural trigger phrases a user would plausibly say ('evernote sdk patterns', 'evernote best practices', 'evernote advanced', 'evernote batch operations'), giving good coverage of relevant terms.

3 / 3

Distinctiveness Conflict Risk

The Evernote SDK niche is narrow and the triggers are domain-specific ('evernote sdk patterns', 'evernote batch operations'), making it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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