CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-webhooks-events

Implement Evernote webhook notifications and sync events. Use when handling note changes, implementing real-time sync, or processing Evernote notifications. Trigger with phrases like "evernote webhook", "evernote events", "evernote sync", "evernote notifications".

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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, lean overview with executable code and a properly structured one-level reference for full implementations. Its main gap is workflow clarity: validation and error-recovery are mentioned but not framed as explicit checkpoints, which is relevant given the batch/distributed nature of webhook sync.

Suggestions

Add an explicit validation checkpoint to the workflow sequence (e.g., 'Verify the sync chunk USN advanced before storing lastUSN; if not, retry after a short delay') rather than only describing idempotency in prose.

Frame a concrete validate→fix→retry loop for duplicate/race-condition handling so the recovery path is a numbered step, not just a row in the error table.

Trim the 'Examples' section or differentiate it from Step 5's polling fallback to remove the duplicated polling-based-sync content.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no preamble explaining what Evernote or webhooks are, each step pairs tight prose with one focused code snippet. The only minor redundancy is the 'Examples' section restating the polling fallback already covered in Step 5, but it does not rise to verbosity.

3 / 3

Actionability

Provides concrete, executable JavaScript with specific Evernote SDK calls and real parameters (e.g., getSyncState(), getFilteredSyncChunk(lastUSN, 100, filter)) for the endpoint and sync steps; the remaining handler/polling detail is delegated to a real reference file rather than left as pseudocode.

3 / 3

Workflow Clarity

The five steps are clearly sequenced, and idempotency and race-condition handling are mentioned (tracking processed USNs; re-sync with delay), but verification is described rather than structured as explicit validate→fix→retry checkpoints in the workflow itself.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview with clearly signaled, one-level-deep navigation to references/implementation-guide.md (verified to exist and contain the full implementation), and content is appropriately split rather than monolithic.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, complete, and distinctive: it names concrete Evernote webhook and sync actions, gives explicit 'Use when' trigger guidance with natural keyword variations, and occupies a clear niche unlikely to conflict with other skills. It matches the top rubric anchors across all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in the Evernote domain — 'Implement Evernote webhook notifications and sync events', 'handling note changes', 'implementing real-time sync', 'processing Evernote notifications' — rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' ('Implement Evernote webhook notifications and sync events') and 'when' ('Use when handling note changes, implementing real-time sync, or processing Evernote notifications') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural phrases a user would actually say — 'evernote webhook', 'evernote events', 'evernote sync', 'evernote notifications' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Evernote-specific webhook/sync niche with distinct triggers, making it unlikely to fire for or conflict with unrelated skills.

3 / 3

Total

12

/

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.