Agent skill · operations · jeremylongshore
evernote-incident-runbook
Manage incident response for Evernote integration issues.
Why this skill is useful
Provides specific diagnostic commands and mitigation strategies for Evernote API incidents that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. Requires evernote account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Evernote Incident Runbook Overview Step-by-step procedures for responding to Evernote integration incidents including API outages, rate limit escalations, authentication failures, data sync issues, and quota exhaustion. Prerequisites Access to monitoring dashboards and production logs Production Evernote API credentials Communication channels for escalation (Slack, PagerDuty) Instructions Incident Classification Severity Symptoms Response Time ---------- ---------- --------------- P1 - Critical All Evernote API calls failing, data loss risk 15 minutes P2 - High Persistent rate limits, auth failures for multiple users 1 hour P3 - Medium Intermittent errors, degraded sync performance 4 hours P4 - Low Single user issues, non-critical feature affected Next business day Step 1: Triage Check Evernote's status page first. If Evernote is down, activate the circuit breaker and wait. Step 2: Rate Limit Escalation If rate limits are persistent: reduce API call frequency, increase delays between batch operations, and contact Evernote developer support for a rate limit increase. Step 3: Authentication Failure For auth failures: verify tokens are not expired (edamexpires), check that production credentials match the production endpoint (sandbox: false), and test with a fresh Developer Token to isolate the issue. Step 4: Sync Failure Recovery For sync issues: compare local USN with server USN via getSyncState(). If gap is too large, reset to full sync from USN 0. Verify data integrity after re-sync. Step 5: Mitigation Strategies Circuit breaker: Disable Evernote API calls after N consecutive failures. Retry after cooldown period. Graceful degradation: Serve cached data when API is unavailable. Queue writes for retry. Failover: Switch to polling-based sync if webhooks stop arriving. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/evernote-incident-runbook--73f690