evernote-performance-tuning
Optimize Evernote integration performance. Use when improving response times, reducing API calls, or scaling Evernote integrations. Trigger with phrases like "evernote performance", "optimize evernote", "evernote speed", "evernote caching".
70
64%
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-performance-tuning/SKILL.mdQuality
Discovery
79%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage, completeness, and distinctiveness due to its narrow Evernote performance niche and explicit trigger guidance. However, it is weak on specificity—it describes goals (improving response times, reducing API calls) rather than concrete actions the skill performs (e.g., implementing caching strategies, batching requests, profiling API usage).
Suggestions
Replace vague outcome phrases with concrete actions, e.g., 'Implements caching layers, batches API requests, profiles slow endpoints, and adds connection pooling for Evernote integrations.'
Add specific technical capabilities like 'rate limit handling', 'pagination optimization', or 'webhook configuration' to make the skill's concrete offerings clearer.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Optimize Evernote integration performance' but does not list concrete actions. 'Improving response times, reducing API calls, or scaling' are vague outcome-oriented phrases rather than specific actionable capabilities like 'implement caching layers, batch API requests, add connection pooling'. | 1 / 3 |
Completeness | The description answers both 'what' (optimize Evernote integration performance) and 'when' (explicit 'Use when' clause with triggers and a 'Trigger with phrases like' section). Both are clearly stated. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases: 'evernote performance', 'optimize evernote', 'evernote speed', 'evernote caching'. These are terms users would naturally say, and the inclusion of 'caching' and 'speed' adds good variation. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Evernote' + 'performance optimization' creates a very specific niche. It is unlikely to conflict with other skills due to the narrow domain focus on Evernote integration performance specifically. | 3 / 3 |
Total | 10 / 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 solid foundation for Evernote performance optimization with good code examples for caching and data retrieval, but falls short on later steps (batching, connection optimization, monitoring) which lack concrete implementations. The error handling table is a strength, but the absence of validation/verification steps and the broken reference to a bundle file weaken the overall quality. The content could be more concise by trimming redundant sections and more actionable by providing executable code for all steps.
Suggestions
Add executable code examples for Steps 3-5 (request batching with getSyncChunk(), client reuse pattern, and monitoring setup) instead of vague descriptions.
Add a validation/verification step — e.g., a script or logging snippet to confirm cache hit rates and measure API call reduction before and after optimization.
Either provide the referenced 'references/implementation-guide.md' bundle file or remove the broken reference and inline the essential content.
Remove the 'Output' section which largely restates what the instructions already cover, and merge the 'Examples' section closer to the relevant steps for better flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., the Prerequisites section, the 'Overview' restating what the skill does, and some verbose descriptions in Steps 3-5 that could be tighter). The code examples are well-targeted but surrounding prose could be trimmed. | 2 / 3 |
Actionability | Steps 1 and 2 have concrete, executable code examples which is good. However, Steps 3-5 are vague descriptions without executable code — 'Use getSyncChunk()' and 'Reuse the Evernote client instance' lack concrete implementation. The batching and monitoring steps describe rather than instruct. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced and the error handling table is a nice addition. However, there are no validation checkpoints — no way to verify caching is working, no benchmarking step to confirm improvements, and no feedback loop for checking if optimizations actually reduced API calls or improved response times. | 2 / 3 |
Progressive Disclosure | References an implementation guide at 'references/implementation-guide.md' which is good progressive disclosure structure, but no bundle files are provided so this reference is broken. The content is reasonably organized with sections, but the Output section and Examples section at the end feel somewhat redundant with the main instructions. | 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.