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".
59
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/evernote-pack/skills/evernote-cost-tuning/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Evernote cost/resource optimization), includes explicit 'Use when' guidance, and provides natural trigger phrases. Its main weakness is that the specific capabilities could be more concrete—listing actual optimization actions rather than general categories like 'managing API quotas' and 'reducing storage usage'.
Suggestions
Add more concrete actions such as 'calculate remaining API rate limits', 'estimate monthly storage consumption', or 'recommend batch upload strategies' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Evernote integration costs/resources) and mentions some actions (managing API quotas, reducing storage usage, optimizing upload limits), but these are somewhat general and don't list multiple concrete, specific actions like 'calculate remaining quota', 'suggest batch strategies', or 'monitor rate limits'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (optimize Evernote integration costs and resource usage) and 'when' (managing API quotas, reducing storage usage, optimizing upload limits) with an explicit 'Use when' clause and trigger phrases. | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger phrases users would say: 'evernote cost', 'evernote quota', 'evernote limits', 'evernote upload'. It also includes related terms like 'API quotas', 'storage usage', and 'upload limits' which cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | The skill is highly specific to Evernote cost/resource optimization, which is a clear niche. The trigger terms are all Evernote-specific and unlikely to conflict with other skills unless there's another Evernote-related skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable structure for Evernote cost optimization with useful reference tables and some executable code, but falls short on actionability for the majority of its steps (3-5 are prose-only). It lacks validation checkpoints for quota-sensitive operations and contains redundant sections (Output repeats the steps, Examples repeat Step 2). Referenced files are not available in the bundle.
Suggestions
Add executable code examples for Steps 3-5, particularly for the storage cleanup and quota alert workflows, rather than describing them in prose.
Add explicit validation/feedback loops: e.g., after attempting an upload, check the response, handle QUOTA_REACHED gracefully, and retry or queue for later.
Remove the redundant Output section and consolidate the Examples section's image pipeline description with Step 2 to reduce token waste.
Either provide the referenced 'references/implementation-guide.md' bundle file or inline the critical implementation details directly in the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., the Overview restates what the description already covers, the Output section is a redundant summary of what was already described in the steps). The account limits table and error handling table are useful reference material, but the Prerequisites section explains things Claude would know. Some tightening is possible. | 2 / 3 |
Actionability | The quota monitoring code is executable and concrete, but Steps 3-5 are vague prose without code examples. The image compression pipeline is described in words ('resize large images', 'convert PNG to JPEG') without actual implementation code. The `estimateNoteSize` and `canUpload` functions are trivial helpers rather than the core optimization logic promised. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical sequence, but there are no explicit validation checkpoints or feedback loops. For operations involving quota management and batch uploads (potentially destructive if quota is exceeded), there's no validate-then-proceed pattern. Step 3 mentions 'check quota before creating notes' but doesn't show how to handle failure or retry. | 2 / 3 |
Progressive Disclosure | The skill references an implementation guide at 'references/implementation-guide.md' and an architecture skill 'evernote-reference-architecture', but no bundle files are provided, so these references are unverifiable. The content is reasonably structured with sections, but the Examples section at the bottom repeats guidance already given in the steps (image pipeline), and the Output section is redundant. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
8a9cd04
- 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.