evernote-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-debug-bundleDebug 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".
Validation
69%| 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 |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
65%This is a comprehensive debugging toolkit with excellent, executable code examples that are immediately actionable. However, it's verbose for a SKILL.md file - the full implementations would be better placed in referenced utility files with the skill providing an overview and usage patterns. The workflow could benefit from explicit diagnostic decision trees rather than just presenting tools.
Suggestions
Add a diagnostic decision tree at the top: 'If auth error → run diagnose, check token section; If ENML error → use validator; If rate limit → check logs for frequency'
Move full code implementations to referenced files (e.g., 'See utils/debug-logger.js') and keep only key usage patterns and examples in the SKILL.md
Add explicit validation checkpoints in the workflow: 'After running diagnose, verify user info appears before proceeding to note creation test'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides comprehensive debugging tools but is quite lengthy (~400 lines). While the code is necessary, some sections could be condensed - the debug logger and instrumented client could be combined or summarized with key patterns rather than full implementations. | 2 / 3 |
Actionability | Excellent actionability with fully executable JavaScript code throughout. All utilities are copy-paste ready with complete implementations, and the CLI commands are specific and immediately usable. | 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' feedback loop for the debugging process itself - it's more of a toolkit than a guided troubleshooting workflow. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the entire implementation is inline rather than split into referenced files. The Error Handling table and Resources section are good, but the bulk of code could be referenced rather than embedded. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the capabilities could be more specific - listing concrete debugging actions rather than general terms like 'diagnostic tools and techniques' would strengthen it.
Suggestions
Replace 'diagnostic tools and techniques' with specific actions like 'analyze error codes, trace authentication flows, parse API response headers, validate OAuth tokens'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote API) and mentions 'diagnostic tools and techniques', 'inspecting requests/responses', but doesn't list specific concrete actions like 'analyze error codes', 'trace authentication flows', or 'parse response headers'. | 2 / 3 |
Completeness | Clearly answers both what (debug Evernote API issues with diagnostic tools) and when (troubleshooting API calls, inspecting requests/responses, diagnosing integration problems) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'debug evernote', 'evernote diagnostic', 'troubleshoot evernote', 'evernote logs', 'inspect evernote'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Evernote API debugging specifically. The explicit 'evernote' keyword throughout makes it unlikely to conflict with general debugging skills or other API tools. | 3 / 3 |
Total | 11 / 12 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.