CtrlK
BlogDocsLog inGet started
Tessl Logo

evernote-cost-tuning

Optimize Evernote integration costs and resource usage. Use when managing API quotas, reducing storage usage, or optimizing upload limits. Trigger with phrases like "evernote cost", "evernote quota", "evernote limits", "evernote upload".

61

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

57%

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

A solid, well-structured skill body with executable core code and good progressive disclosure via a single real reference file. Weaknesses are mild redundancy and missing executable code/feedback loops in the later, more destructive steps.

Suggestions

Tighten the 'Examples' and 'Output' sections, which repeat guidance already in Steps 1-2, to improve token efficiency.

Add executable code or concrete commands for Steps 3-5 (metadata reads, batching, large-note cleanup, alerting) rather than descriptive direction.

Add an explicit validation/feedback loop for the destructive cleanup step (e.g., verify reclaimed quota after deleting trash notes before declaring success).

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the 'Examples' section repeats image-pipeline guidance already stated in Step 2 and the 'Output' list restates capabilities, so it could be tightened; not the lean level-3 nor a padded level-1.

2 / 3

Actionability

Steps 1-2 provide fully executable JavaScript (getQuotaStatus, estimateNoteSize, canUpload), but Steps 3-5 ('Use findNotesMetadata()', 'Batch small notes', 'Send alerts when...') give only descriptive guidance without executable code, leaving the overall guidance concrete-but-incomplete.

2 / 3

Workflow Clarity

The five steps are clearly sequenced and include implicit pre-checks (quota check, canUpload, skip oversized files), but there is no explicit validate->fix->retry feedback loop for the destructive/batch operations (deleting trash notes, removing resources, batching), which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

SKILL.md is an overview with a single well-signaled, one-level-deep reference to references/implementation-guide.md (a real bundle file), with detail appropriately split out and easy navigation; matches the level-3 anchor.

3 / 3

Total

9

/

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.

A well-formed description with explicit what/when guidance and natural Evernote-specific trigger phrases. The only weakness is moderate specificity: the named actions are somewhat abstract rather than a crisp list of concrete operations.

DimensionReasoningScore

Specificity

Names the Evernote cost domain and several actions ('managing API quotas, reducing storage usage, or optimizing upload limits'), but the verbs are abstract rather than the multiple concrete operations seen in the level-3 anchor; not a level-3 list of distinct concrete actions, and not a level-1 vague one-liner.

2 / 3

Completeness

States what it does ('Optimize Evernote integration costs and resource usage') and when to use it via an explicit 'Use when managing API quotas...' clause plus a 'Trigger with phrases like...' list, satisfying both what and when with explicit triggers.

3 / 3

Trigger Term Quality

Explicit trigger phrases 'evernote cost', 'evernote quota', 'evernote limits', 'evernote upload' plus 'API quotas', 'storage usage', 'upload limits' give good coverage of natural terms a user would actually say; clearly above the level-2 'some relevant keywords' anchor.

3 / 3

Distinctiveness Conflict Risk

Evernote-scoped cost/quota triggers are a clear niche unlikely to fire for unrelated skills; well above the level-2 'could still overlap' anchor.

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.