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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-cost-tuning73
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-structured skill description with explicit 'Use when' and 'Trigger with' clauses that clearly define its scope. The Evernote-specific focus and cost/quota optimization niche make it highly distinctive. The main weakness is that the capabilities could be more concrete with specific actions rather than general categories.
Suggestions
Add more specific concrete actions like 'analyze API call patterns', 'compress note attachments', 'identify large notes consuming storage', or 'track monthly upload usage'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote integration) and mentions some actions (managing API quotas, reducing storage usage, optimizing upload limits), but these are somewhat general categories rather than multiple specific concrete actions like 'analyze quota usage patterns' or 'compress attachments'. | 2 / 3 |
Completeness | Clearly answers both what (optimize Evernote integration costs and resource usage) and when (managing API quotas, reducing storage usage, optimizing upload limits) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'evernote cost', 'evernote quota', 'evernote limits', 'evernote upload'. These are practical terms users would naturally use when facing these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Evernote cost/quota optimization. The explicit Evernote-specific triggers and focus on costs/limits makes it highly 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 comprehensive, executable code for Evernote quota management but suffers from severe verbosity - the same formatBytes helper appears four times, and extensive class boilerplate inflates token usage. The actionability is excellent with real SDK patterns, but the content would benefit greatly from condensing to key patterns and moving detailed implementations to referenced files.
Suggestions
Condense to key patterns and API calls (quota check, image optimization, cleanup queries) rather than full class implementations - reduce by 60-70%
Extract repeated utilities (formatBytes, wrapENML) to a single referenced utility file
Add explicit validation workflow: 'Before any upload: 1. Check quota 2. If >80% used, optimize resources 3. Verify size fits 4. Proceed or abort'
Move detailed class implementations to separate referenced files (e.g., 'See quota-service.js for full implementation')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with 400+ lines of code. The account limits table is useful, but the extensive JavaScript classes include many helper methods (formatBytes repeated 4 times) and boilerplate that Claude could generate. Much of this could be condensed to key patterns and API calls. | 1 / 3 |
Actionability | Provides fully executable JavaScript code with complete class implementations, specific API calls, and copy-paste ready examples. The code is concrete and includes real Evernote SDK usage patterns. | 3 / 3 |
Workflow Clarity | Steps are numbered but lack validation checkpoints. For quota-sensitive operations, there's no explicit 'verify quota before proceeding' workflow or error recovery guidance. The checklist at the end is helpful but the main workflow lacks feedback loops. | 2 / 3 |
Progressive Disclosure | Content is monolithic with all code inline. The account limits table and checklist are well-placed, but the six large code blocks should be referenced files rather than inline. Only references external resources at the end. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (675 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 11 Passed | |
- 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.