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".
71
66%
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 description with strong completeness and distinctiveness, clearly scoping to Evernote API debugging with explicit trigger guidance. Its main weakness is that the 'what' portion is somewhat general — it mentions 'diagnostic tools and techniques' without specifying what those tools or techniques are, which limits specificity.
Suggestions
Add specific concrete actions such as 'parse API error codes, replay failed requests, validate OAuth tokens, analyze rate limit headers' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Evernote API debugging) and mentions some actions like 'inspecting requests/responses' and 'diagnosing integration problems', but doesn't list multiple specific concrete actions (e.g., what diagnostic tools, what specific techniques, what kinds of issues it resolves). | 2 / 3 |
Completeness | Clearly answers both 'what' (debug Evernote API issues with diagnostic tools and techniques) and 'when' (troubleshooting API calls, inspecting requests/responses, diagnosing integration problems), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms: 'debug evernote', 'evernote diagnostic', 'troubleshoot evernote', 'evernote logs', 'inspect evernote', plus contextual phrases like 'API calls', 'requests/responses', and 'integration problems'. These cover natural variations a user would say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Evernote API debugging, which is a narrow niche unlikely to conflict with other skills. The trigger terms are all Evernote-specific. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable structure for Evernote API debugging with some executable code in the first two steps, but falls short by leaving Steps 3-5 as vague descriptions without code, deferring to a non-existent implementation guide. The error handling table is useful, but the lack of validation checkpoints in the workflow and broken references to bundle files significantly weaken the skill's utility.
Suggestions
Either include the referenced 'references/implementation-guide.md' bundle file or inline the executable code for Steps 3-5 (ENML validator, token inspector, diagnostic CLI) directly in the SKILL.md.
Add explicit validation/feedback loops to the workflow, e.g., 'Run diagnose command → review output → fix identified issues → re-run to confirm resolution.'
Remove explanatory prose before code blocks (e.g., 'Wrap the NoteStore with a Proxy that automatically logs every API call...') since Claude can infer purpose from the code itself.
Ensure all cross-references (evernote-common-errors, evernote-rate-limits) either exist as bundle files or are removed to avoid broken navigation.
| 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 each step does before showing code, which Claude could infer. However, it's not egregiously verbose. | 2 / 3 |
Actionability | Steps 1-2 provide executable JavaScript code, but Steps 3-5 are purely descriptive with no code at all—just vague instructions like 'Create a CLI script with commands.' The reference to implementation-guide.md for the full code doesn't exist in the bundle, leaving those steps unactionable. | 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 (e.g., 'run validator, if errors fix and re-run'). The workflow is more of a component list than a clear debugging sequence. | 2 / 3 |
Progressive Disclosure | The skill references 'references/implementation-guide.md' and 'evernote-common-errors' and 'evernote-rate-limits' but no bundle files exist. This creates broken references. Steps 3-5 defer all code to a non-existent file, making the skill incomplete without those references. | 1 / 3 |
Total | 7 / 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.