Skip to content
Back to skills

Evernote Debug Bundle

ASecurity

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".

  • 4 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 10, 2026
toolsphpbashnodedebuggingapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill evernote-debug-bundle --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evernote Debug Bundle?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Evernote Debug Bundle
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-evernote-debug-bundle/badge)](https://www.skillsdirectory.com/skills/micsapp-evernote-debug-bundle)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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
---
# Evernote Debug Bundle

## Overview
Comprehensive debugging toolkit for Evernote API integrations, including request logging, ENML validation, token inspection, and diagnostic utilities.

## Prerequisites
- Evernote SDK installed
- Node.js environment
- Understanding of common Evernote errors

## Instructions

### Step 1: Debug Logger

### Step 2: Instrumented Client Wrapper

### Step 3: ENML Validator

### Step 4: Token Inspector

### Step 5: Diagnostic CLI

### Step 6: Package.json Scripts

For full implementation details and code examples, load:
`references/implementation-guide.md`

## Output
- Debug logger with request/response tracking
- Instrumented client wrapper for automatic logging
- ENML validator with auto-fix capability
- Token and account inspector
- Diagnostic CLI script

## Error Handling
| Issue | Diagnostic | Solution |
|-------|------------|----------|
| Auth failures | Check token in logs | Re-authenticate |
| ENML errors | Use ENMLValidator | Auto-fix with validator |
| Rate limits | Check request frequency in logs | Add delays |
| Missing data | Inspect response logs | Check API parameters |

## Resources
- [Error Handling](https://dev.evernote.com/doc/articles/error_handling.php)
- [ENML DTD](http://xml.evernote.com/pub/enml2.dtd)
- [API Reference](https://dev.evernote.com/doc/reference/)

## Next Steps
For rate limit handling, see `evernote-rate-limits`.

## Examples

**Basic usage**: Apply evernote debug bundle to a standard project setup with default configuration options.

**Advanced scenario**: Customize evernote debug bundle for production environments with multiple constraints and team-specific requirements.

Files in this skill

  • SKILL.md2.2 KB
  • references/implementation-guide.md16.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.