| name | evernote-debug-bundle |
| description | 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".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(node:*), Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| compatible-with | claude-code, codex, openclaw |
| tags | ["saas","evernote","api","debugging"] |
Evernote Debug Bundle
Current State
!node --version 2>/dev/null || echo 'N/A'
!python3 --version 2>/dev/null || echo 'N/A'
Overview
Comprehensive debugging toolkit for Evernote API integrations, including request/response logging, ENML validation with auto-fix, token inspection, and diagnostic CLI utilities.
Prerequisites
- Evernote SDK installed
- Node.js environment
- Understanding of common Evernote errors (see
evernote-common-errors)
Instructions
Step 1: Debug Logger
Create a logger that captures API method names, arguments (with token redaction), response times, and error details. Write to both console and file for post-mortem analysis.
class EvernoteDebugLogger {
constructor(logFile = 'evernote-debug.log') {
this.logFile = logFile;
this.requests = [];
}
logRequest(method, args, response, duration, error) {
const entry = {
timestamp: new Date().toISOString(),
method,
duration: `${duration}ms`,
success: !error,
error: error?.message || error?.errorCode
};
this.requests.push(entry);
fs.appendFileSync(this.logFile, JSON.stringify(entry) + '\n');
}
}
Step 2: Instrumented Client Wrapper
