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".
77
73%
Does it follow best practices?
Impact
Pending
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 with excellent completeness and distinctiveness, featuring explicit 'Use when' and 'Trigger with' clauses that clearly scope it to Evernote resource optimization. The main weakness is that the specific capabilities could be more concrete—listing actual actions rather than general optimization areas would strengthen it. Overall it performs well for skill selection purposes.
Suggestions
Add more concrete actions to improve specificity, e.g., 'Calculate remaining API rate limits, suggest batch upload strategies, estimate storage consumption, recommend note compression techniques.'
| 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, optimizing upload limits) with an explicit 'Use when' clause and trigger phrases. | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger phrases ('evernote cost', 'evernote quota', 'evernote limits', 'evernote upload') that users would naturally say, and also includes terms like 'API quotas', 'storage usage', and 'upload limits' which are relevant keywords. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Evernote cost/resource optimization, which is a clear niche. The trigger terms all include 'evernote' combined with cost/quota/limits, making it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is reasonably well-structured with good progressive disclosure and useful reference tables, but falls short on actionability for Steps 3-5 which lack concrete code. The workflow would benefit from explicit validation checkpoints (e.g., verify quota before and after upload) and the content could be tightened by removing the Output section and trimming prose descriptions.
Suggestions
Add executable code examples for Steps 3-5 (efficient note creation with pre-upload check, storage cleanup query, and alert threshold logic) instead of prose descriptions.
Add explicit validation checkpoints in the workflow, e.g., 'Check quota status → if below threshold, compress resources → re-check estimated size → only then upload → verify upload succeeded and log new quota status'.
Remove the Output section (it just restates what the steps describe) and trim the Overview to reduce redundancy with the skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., the Overview section restates the description, the Output section lists bullet points that don't add actionable value, and some steps like Step 3 are vague filler). The account limits table is useful reference but the overall content could be tightened. | 2 / 3 |
Actionability | Steps 1-2 provide executable JavaScript code, but Steps 3-5 are vague descriptions without concrete code. The image compression pipeline is described in prose but not implemented. The `estimateNoteSize` and `canUpload` functions are trivial and don't demonstrate the actual optimization work (compression, cleanup, batching). | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically, but there are no validation checkpoints or feedback loops. For operations that could hit quota limits or fail (uploading, cleanup), there's no explicit validate-then-proceed pattern. The error handling table is helpful but disconnected from the workflow steps. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, references an implementation guide for detailed utilities, links to external resources, and points to a related architecture skill. The reference table is appropriately inline as quick-reference material. Navigation is clear and one level deep. | 3 / 3 |
Total | 9 / 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
70e9fa4
- 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.