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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-debug-bundle79
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 excellent trigger term coverage and clear completeness. The main weakness is that the specific capabilities could be more concrete - listing actual diagnostic actions rather than general categories like 'diagnostic tools and techniques'. The explicit trigger phrase list is a strong feature that aids skill selection.
Suggestions
Replace 'diagnostic tools and techniques' with specific actions like 'analyze error responses, trace request headers, validate OAuth tokens, inspect rate limits'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote API) and mentions 'diagnostic tools and techniques', 'inspecting requests/responses', but doesn't list multiple concrete specific actions like 'analyze error codes', 'trace request headers', or 'validate authentication tokens'. | 2 / 3 |
Completeness | Clearly answers both what ('Debug Evernote API issues with diagnostic tools and techniques') and when ('Use when troubleshooting API calls, inspecting requests/responses, or diagnosing integration problems') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'debug evernote', 'evernote diagnostic', 'troubleshoot evernote', 'evernote logs', 'inspect evernote', plus contextual phrases like 'API calls' and 'integration problems'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Evernote API debugging specifically. The combination of 'Evernote' + 'API' + 'debug/diagnostic' creates a clear, distinct trigger space unlikely to conflict with general debugging or other API skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 debugging tools for Evernote API integration with excellent actionability. However, it's verbose with full class implementations inline rather than referenced, and lacks clear diagnostic workflows with explicit decision points. The content would benefit from restructuring into an overview with referenced implementation files.
Suggestions
Add a 'Quick Diagnostic Workflow' section at the top with numbered steps: 1) Run diagnose, 2) Check specific output, 3) If error X, see section Y
Move full class implementations to separate reference files (e.g., DEBUG-LOGGER.md, ENML-VALIDATOR.md) and keep only usage examples in SKILL.md
Add explicit validation checkpoints in the workflow, e.g., 'If connection test fails with errorCode 4, STOP and re-authenticate before proceeding'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides comprehensive debugging tools but is quite lengthy (~400 lines). While the code is useful, some sections could be condensed - the full class implementations could be referenced rather than inline, and Claude doesn't need complete implementations of standard patterns like log rotation or byte formatting. | 2 / 3 |
Actionability | Excellent actionability with fully executable JavaScript code, complete class implementations, CLI scripts, and package.json configurations. All code is copy-paste ready with clear usage examples at the end. | 3 / 3 |
Workflow Clarity | The skill presents tools in numbered steps but lacks a clear diagnostic workflow with validation checkpoints. There's no explicit 'if X fails, do Y' guidance beyond the error table. The diagnostic CLI runs tests but doesn't guide users through interpreting results or next actions. | 2 / 3 |
Progressive Disclosure | The skill is largely monolithic with all code inline. The Resources section provides external links and references another skill (evernote-rate-limits), but the main content could benefit from splitting detailed implementations into separate reference files while keeping SKILL.md as an overview. | 2 / 3 |
Total | 9 / 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 (676 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.