evernote-debug-bundle
Debug Evernote API issues with diagnostic tools and techniques. Use when troubleshooting API calls, inspecting requests/responses, or diagnosing integration problems. Trigger with phrases like "debug evernote", "evernote diagnostic", "troubleshoot evernote", "evernote logs", "inspect evernote".
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-debug-bundle/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 well-structured skill description with strong completeness and distinctiveness. It clearly identifies when to use the skill with explicit trigger phrases and a 'Use when' clause. The main weakness is that the specific capabilities could be more concrete — listing actual diagnostic actions rather than general terms like 'diagnostic tools and techniques'.
Suggestions
Replace 'diagnostic tools and techniques' with specific actions like 'parse API error codes, replay failed requests, validate OAuth tokens, inspect rate limit headers'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote API debugging) and mentions 'diagnostic tools and techniques', 'inspecting requests/responses', and 'diagnosing integration problems', but doesn't list specific concrete actions like 'parse error codes', 'replay failed requests', or 'validate OAuth tokens'. | 2 / 3 |
Completeness | Clearly answers both 'what' (debug Evernote API issues with diagnostic tools, inspect requests/responses, diagnose integration problems) and 'when' (explicit 'Use when' clause plus 'Trigger with phrases like' section providing concrete activation guidance). | 3 / 3 |
Trigger Term Quality | Includes a good range of natural trigger phrases: 'debug evernote', 'evernote diagnostic', 'troubleshoot evernote', 'evernote logs', 'inspect evernote', plus terms like 'API calls', 'requests/responses', and 'integration problems' that users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Evernote API debugging is highly distinctive and unlikely to conflict with other skills. The combination of 'Evernote' + 'API' + 'debug/diagnostic' creates a clear, narrow scope. | 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 has good structure and progressive disclosure, with a clear overview that points to detailed references. However, it suffers from incomplete actionability — Steps 3-5 describe what to build without providing executable code, making half the skill descriptive rather than instructive. The workflow could benefit from explicit validation checkpoints, especially around the ENML validation and auto-fix cycle.
Suggestions
Provide executable code snippets for Steps 3-5 (ENML validator, token inspector, CLI) or remove the prose descriptions and simply reference the implementation guide directly, since the current descriptions are neither concise nor actionable.
Add an explicit feedback loop for ENML validation: validate -> review errors -> auto-fix -> re-validate -> confirm clean output.
Trim explanatory phrases like 'This adds zero-config debugging to any existing integration' and 'Write to both console and file for post-mortem analysis' — Claude doesn't need motivation for why a pattern is useful.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory text (e.g., 'This adds zero-config debugging to any existing integration', 'Write to both console and file for post-mortem analysis') and describes what code should do rather than just showing it. Steps 3-5 are described in prose without code, which is verbose without being actionable. | 2 / 3 |
Actionability | Steps 1-2 provide executable JavaScript code, but Steps 3-5 are purely descriptive with no concrete code or commands. The CLI step says 'Create a CLI script with commands' without showing how. The reference to implementation-guide.md defers the actual executable content elsewhere. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced, and the error handling table provides diagnostic-to-solution mappings. However, there are no explicit validation checkpoints or feedback loops — for a debugging toolkit that involves ENML validation and auto-fix, there's no 'validate -> fix -> re-validate' loop explicitly stated in the workflow. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with inline essentials (Steps 1-2 code) and appropriately defers the full implementation to a single reference file (references/implementation-guide.md). External resources are well-signaled, and the cross-references to related skills (evernote-common-errors, evernote-rate-limits) are 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.