CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-rate-limits

Handle Evernote API rate limits effectively. Use when implementing rate limit handling, optimizing API usage, or troubleshooting rate limit errors. Trigger with phrases like "evernote rate limit", "evernote throttling", "api quota evernote", "rate limit exceeded".

61

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/evernote-pack/skills/evernote-rate-limits/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The skill is well-structured with good progressive disclosure and a useful error-handling table, but is held back by a code bug in Step 2, a prose-only Step 3, minor prerequisite fluff, and no explicit validation loop for batch operations.

Suggestions

Fix the broken Step 2 wrapper code: 'this.noteStoremethod' is missing a property-access operator (e.g. this.noteStore[method](...args)).

Add an executable code sample for Step 3's batch processing instead of describing it only in prose.

Add an explicit verify/retry checkpoint to the batch workflow (e.g. validate partial results before proceeding) to satisfy the feedback-loop requirement for batch operations.

DimensionReasoningScore

Conciseness

The body is mostly action-dense with code and a useful error-handling table, but the Prerequisites section lists concepts Claude already knows ('Understanding of async/await patterns', 'Error handling implementation') that could be trimmed, so it is not fully lean.

2 / 3

Actionability

Executable JS is provided for the retry handler and client wrapper, but the Step 2 wrapper contains broken code ('this.noteStoremethod' is missing the method-access operator) and Step 3's batch processing is described only in prose without code, leaving guidance incomplete.

2 / 3

Workflow Clarity

Steps 1-5 are clearly sequenced, but the batch operation in Step 3 lacks an explicit validate/verify checkpoint and feedback loop, which the rubric caps at 2 for batch operations.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview that points to a single one-level-deep reference (references/implementation-guide.md, verified to exist) with a clearly signaled link, splitting detail appropriately.

3 / 3

Total

9

/

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 well-formed description that answers both what and when with natural, distinctive trigger phrases. The only weakness is that the named actions are somewhat generic verbs rather than concrete operations.

DimensionReasoningScore

Specificity

Names the domain ('Evernote API rate limits') and several actions ('implementing rate limit handling, optimizing API usage, troubleshooting rate limit errors'), but the verbs are generic abstractions rather than concrete operations, so it stops short of the multi-action score-3 anchor.

2 / 3

Completeness

It clearly states what the skill does ('Handle Evernote API rate limits effectively') and when to use it ('Use when implementing rate limit handling, optimizing API usage, or troubleshooting rate limit errors') with explicit triggers, satisfying both what and when.

3 / 3

Trigger Term Quality

Explicit trigger phrases like 'evernote rate limit', 'evernote throttling', 'api quota evernote', and 'rate limit exceeded' are natural terms a user would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Evernote-specific scoping and 'evernote'-prefixed trigger phrases carve out a clear niche, making it 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.