CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-performance-tuning

Optimize Evernote integration performance. Use when improving response times, reducing API calls, or scaling Evernote integrations. Trigger with phrases like "evernote performance", "optimize evernote", "evernote speed", "evernote caching".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

A well-structured, actionable, and token-efficient skill body that offloads detail to a real reference file. The main gap is the absence of explicit validation/verification checkpoints in the optimization workflow, particularly around batch operations.

Suggestions

Add an explicit validation/verification checkpoint after Step 3 (Request Batching) — e.g., confirm the sync chunk count and retry on RATE_LIMIT_REACHED before proceeding.

Include a brief feedback loop (measure -> compare p95/cache hit rate -> adjust TTL) in Step 5 so the monitoring step drives iterative tuning rather than only alerting.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, never explaining what Evernote or caching is; every section (overview, code, error table, examples) earns its place without padding.

3 / 3

Actionability

It provides fully executable JavaScript (the EvernoteCache class), concrete API calls with specific parameters (findNotesMetadata, getNote(guid, true, false, false, false)), concrete TTL values, and a solutions-oriented error table.

3 / 3

Workflow Clarity

Steps 1-5 are clearly sequenced, but there are no explicit validation or verification checkpoints, and the rubric caps workflow clarity at 2 when batch operations (sync chunk batching) lack feedback loops.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview with a single clearly-signaled, one-level-deep reference to the verified-existing references/implementation-guide.md, keeping detail out of the main file.

3 / 3

Total

11

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 strong description with an explicit Use-when trigger clause, natural trigger phrases, and a distinct Evernote-specific niche. Its only weakness is that the stated capabilities are somewhat general rather than enumerating the concrete optimization techniques the skill actually covers.

DimensionReasoningScore

Specificity

The phrase 'Optimize Evernote integration performance' names the domain and a general action, and 'improving response times, reducing API calls, or scaling Evernote integrations' lists some actions, but these read as use-case triggers rather than a comprehensive set of concrete capabilities (e.g. caching, batching, connection reuse).

2 / 3

Completeness

It explicitly states what it does ('Optimize Evernote integration performance') and when to use it via an explicit 'Use when...' clause, satisfying both required parts.

3 / 3

Trigger Term Quality

Phrases like "evernote performance", "optimize evernote", "evernote speed", and "evernote caching" are natural terms a user would say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Evernote-specific niche and evernote-prefixed trigger phrases make it clearly distinguishable and unlikely to fire for unrelated skills.

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.