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
ENML validation and auto-fix
XML declaration check
0%
100%
DOCTYPE check
0%
100%
en-note root element check
70%
100%
Forbidden elements detection
100%
100%
Forbidden attributes detection
100%
100%
Void element warnings
0%
100%
en-media hash validation
100%
100%
Size warning threshold
0%
100%
fix() removes forbidden elements
50%
100%
fix() corrects void elements
0%
100%
Without context: $0.3373 · 1m 35s · 16 turns · 17 in / 5,718 out tokens
With context: $0.5686 · 1m 47s · 25 turns · 23 in / 6,575 out tokens
Request/response debug logging
Env var toggle
0%
100%
Token redaction
100%
100%
Password redaction
100%
100%
Content truncation
80%
100%
Console log format
0%
100%
Log entry timestamp
100%
100%
Log file rotation
100%
100%
Proxy-based wrapping
100%
100%
Duration logging
100%
50%
Lazy store initialization
0%
100%
Without context: $0.4395 · 1m 57s · 19 turns · 20 in / 7,148 out tokens
With context: $0.8410 · 3m 14s · 26 turns · 98 in / 12,141 out tokens
Diagnostic CLI and token inspection
dotenv usage
100%
100%
Script file location
100%
100%
diagnose npm script
100%
100%
diagnose:verbose npm script
0%
100%
validate:enml npm script
0%
100%
errorCode 4 handling
0%
100%
errorCode 5 handling
0%
100%
Notebook limit constant
0%
100%
Tag limit constant
0%
100%
Per-operation error collection
0%
100%
Without context: $0.4749 · 2m 30s · 21 turns · 70 in / 8,973 out tokens
With context: $0.8226 · 3m 1s · 31 turns · 30 in / 10,189 out tokens
Table of Contents
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.