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".
74
70%
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 explicit trigger guidance and a clear 'Use when' clause. Its main weakness is that the capabilities described are somewhat general—'optimize costs', 'manage quotas'—without listing the specific concrete actions the skill performs. The trigger terms and distinctiveness are strong.
Suggestions
Add more specific concrete actions, e.g., 'Calculate remaining API rate limits, suggest batch upload strategies, estimate storage consumption per notebook, 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 are all Evernote-specific and unlikely to conflict with other skills. | 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.
This skill provides a reasonable framework for Evernote cost optimization with useful reference tables and some executable code, but falls short on actionability for steps 3-5 which lack concrete implementations. The workflow lacks validation checkpoints important for destructive operations like storage cleanup, and the content could be tightened by removing redundant sections (Output, repeated examples).
Suggestions
Add executable code for Steps 3-5, particularly the storage cleanup step which currently has no implementation and involves destructive operations
Add explicit validation checkpoints before destructive operations (e.g., confirm before deleting notes in Step 4, verify quota status before batch uploads in Step 3)
Remove the Output section (it restates the instructions) and consolidate the Examples section content into the relevant instruction steps to reduce redundancy
Provide the referenced 'references/implementation-guide.md' bundle file or remove the reference if it doesn't exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., the Prerequisites section explaining account tiers, the Output section listing bullet points that restate what was already covered, and the Examples section describing things already explained in the instructions). However, it's not egregiously verbose and the tables are useful reference material. | 2 / 3 |
Actionability | Steps 1-2 have executable JavaScript code, but the code is incomplete (e.g., no actual image compression implementation, just size estimation). Steps 3-5 are vague prose with no concrete code or commands. The image pipeline example at the end describes what to do but doesn't show how. | 2 / 3 |
Workflow Clarity | The 5-step sequence is logical and clearly ordered, but there are no explicit validation checkpoints or feedback loops. For operations involving quota management and potential data loss (storage cleanup, batch operations), there should be verify-before-proceeding steps. The cleanup step (Step 4) mentions deleting notes but has no safeguards. | 2 / 3 |
Progressive Disclosure | The skill references an implementation guide at 'references/implementation-guide.md' and an architecture skill, which is good structure. However, no bundle files are provided, so the reference is unverifiable. The Account Limits table and Error Handling table are appropriately inline, but the content is somewhat monolithic with the Examples section repeating earlier content. | 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
3a2d27d
- 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.