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

66

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

72%

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

The content is well-organized and concisely scoped, with good progressive disclosure via a single real reference file. It loses points on actionability due to a broken code example and a code-less batch step, and on workflow clarity for missing explicit validation checkpoints in batch operations.

Suggestions

Fix the malformed code in Step 2 ('this.noteStoremethod)') so it correctly invokes the NoteStore method with args, making the example executable.

Add concrete code for Step 3 (batch operations) rather than prose-only description, since the other steps set an executable-code expectation.

Insert explicit validation checkpoints into the batch workflow (e.g., verify retry limits reached, confirm failures collected before reporting success) to support error recovery.

DimensionReasoningScore

Conciseness

The body is lean and efficient, with brief concrete code and an Overview that does not pad with concepts Claude already knows; the only mild slack is the generic Prerequisites bullets.

3 / 3

Actionability

Steps 1 and 2 provide executable JavaScript, but Step 2's code is malformed ('this.noteStoremethod)') and Step 3 offers only prose, so guidance is incomplete and not fully copy-paste ready.

2 / 3

Workflow Clarity

Five steps are clearly sequenced with a retry loop and an error-handling table, but for batch operations there are no explicit validation/verify checkpoints or feedback loops.

2 / 3

Progressive Disclosure

The body is a concise overview that links once to references/implementation-guide.md (a real, one-level-deep file), with content appropriately split and clearly signaled.

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-formed with explicit 'Use when' triggers and natural trigger phrases, giving it strong completeness and distinctiveness. Specificity is the weakest dimension because it states only one broad action rather than enumerating concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and a clear action ('Handle Evernote API rate limits effectively') but lists only one broad action rather than multiple specific concrete actions like retry, backoff, or monitoring.

2 / 3

Completeness

Explicitly answers both what (handle rate limits) and when ('Use when implementing rate limit handling, optimizing API usage, or troubleshooting rate limit errors') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Trigger phrases like 'evernote rate limit', 'evernote throttling', 'api quota evernote', and 'rate limit exceeded' are natural terms a user would say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The Evernote rate-limit niche with these specific triggers is 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.